Re: [dpdk-dev] Intel fortville not working with multi-segment

[Nissim Nisimov <NissimN@Radware.com>]

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