From: Nissim Nisimov <NissimN@Radware.com>
To: "Zhang, Helin" <helin.zhang@intel.com>
Cc: "'dev@dpdk.org'" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Intel fortville not working with multi-segment
Date: Thu, 14 May 2015 15:48:30 +0000 [thread overview]
Message-ID: <94AA676E9B9A384A844E7692F3CAD90642442ADF@ILMB1.corp.radware.com> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A85B341@SHSMSX104.ccr.corp.intel.com>
Hi Helin,
Any news regarding this issue? do u know if there is any related patch I can apply on my application in order to work with multi-segment packets?
Thanks,
Nissim
-----Original Message-----
From: Zhang, Helin [mailto:helin.zhang@intel.com]
Sent: Tuesday, May 12, 2015 11:51 AM
To: Nissim Nisimov
Cc: 'dev@dpdk.org'
Subject: RE: Intel fortville not working with multi-segment
Hi Nissim
It seems that our validation guys here can reproduce it in our lab. I will check that soon later, and update you later.
Thank you very much for the good finding!
Regards,
Helin
> -----Original Message-----
> From: Nissim Nisimov [mailto:NissimN@Radware.com]
> Sent: Monday, May 11, 2015 11:44 AM
> To: Zhang, Helin
> Cc: 'dev@dpdk.org'
> Subject: RE: Intel fortville not working with multi-segment
>
> Hi,
>
> I am using PF pass-through and it doesn't work even with 2000 bytes of
> server response page size.
> Looks like the first segment of each session is not received.
>
> When i am changing the server response size to 1000 bytes, all works
> as expected.
>
> I am working with dpdk 1.8 version.
>
> Any idea why ? Is it related to i40e multi segment support?
>
> Thx
> Nissim
>
> On May 11, 2015 5:03 AM, "Zhang, Helin" <helin.zhang@intel.com>
> wrote:
> >
> > Hi Nissim
> >
> > Are you using PF pass-through or VF pass-through?
> > For PF pass-through, you might have already gotten the fix.
> > For VF pass-through, there is
>
> Hi Nissim
>
> Are you using PF pass-through or VF pass-through?
> For PF pass-through, you might have already gotten the fix.
> For VF pass-through, there is a bug fix which is needed for supporting
> jumbo frame and multiple mbuf.
> http://www.dpdk.org/dev/patchwork/patch/4641/
>
>
> Regards,
> Helin
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Nissim Nisimov
> > Sent: Monday, May 11, 2015 3:48 AM
> > To: Nissim Nisimov; 'dev@dpdk.org'
> > Subject: Re: [dpdk-dev] Intel fortville not working with
> > multi-segment
> >
> > Hi,
> >
> > can someone assist regarding this issue?
> >
> > Is it a known limitation in i40e/dpdk (no support for multi-segment)?
> >
> > Thx
> > Nissim
> >
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Nissim Nisimov
> > Sent: Thursday, May 07, 2015 5:44 PM
> > To: 'dev@dpdk.org'
> > Subject: [dpdk-dev] Intel fortville not working with multi-segment
> >
> > Hi,
> >
> >
> >
> > I am trying to work with Intel Fortville (XL710) NICs in Passthrough
> > mode from a VM running dpdk app.
> >
> >
> > First I didn't have any TX traffic from the VM, I got dpdk patch for
> > this issue and it fixed it.
> > (http://www.dpdk.org/dev/patchwork/patch/4588/)
> >
> > But now I see that when trying to run multi-segment traffic not all
> > the packets reaching the VM (I tested it on bare metal as well and
> > saw the same issue)
> >
> > Is it a known issue? any workaround for it?
> >
> > Thanks,
> > Nissim
next prev parent reply other threads:[~2015-05-14 15:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 17:58 [dpdk-dev] Queries on DPDK working with XL710 intel NIC Nissim Nisimov
2015-03-20 14:55 ` Nissim Nisimov
2015-03-20 15:30 ` Roberts, Lee A.
2015-04-02 10:26 ` [dpdk-dev] calling rte_eth_rx_queue_setup from secondary processes Nissim Nisimov
2015-05-07 14:43 ` [dpdk-dev] Intel fortville not working with multi-segment Nissim Nisimov
2015-05-10 19:48 ` Nissim Nisimov
2015-05-11 2:02 ` Zhang, Helin
2015-05-11 3:43 ` Nissim Nisimov
2015-05-12 8:50 ` Zhang, Helin
2015-05-14 15:48 ` Nissim Nisimov [this message]
2015-05-27 3:54 ` Zhang, Helin
2015-05-28 17:51 ` Nissim Nisimov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=94AA676E9B9A384A844E7692F3CAD90642442ADF@ILMB1.corp.radware.com \
--to=nissimn@radware.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).