DPDK patches and discussions
 help / color / mirror / Atom feed
From: Nissim Nisimov <NissimN@Radware.com>
To: Nissim Nisimov <NissimN@Radware.com>, "'dev@dpdk.org'" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Intel fortville not working with multi-segment
Date: Sun, 10 May 2015 19:48:03 +0000	[thread overview]
Message-ID: <94AA676E9B9A384A844E7692F3CAD90642432170@ILMB1.corp.radware.com> (raw)
In-Reply-To: <94AA676E9B9A384A844E7692F3CAD90642428A41@ILMB1.corp.radware.com>

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

  reply	other threads:[~2015-05-10 19: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 [this message]
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
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=94AA676E9B9A384A844E7692F3CAD90642432170@ILMB1.corp.radware.com \
    --to=nissimn@radware.com \
    --cc=dev@dpdk.org \
    /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).