From: Bill Bonaparte <programme110@gmail.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: Garik E <kiragon@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] No RX frames on Intel 82599 VF
Date: Wed, 19 Apr 2017 17:49:41 +0800 [thread overview]
Message-ID: <CAO8FX+SZhN9NY1aq4euJAN1fLb24rgQMfy+6D6QcAFRPkgo7mA@mail.gmail.com> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC09090348F9CF@shsmsx102.ccr.corp.intel.com>
I have the same problem on my 82599 nic, after I turnoff the jumbo_frame,
it works.
you can try rte_eth_dev_configure with the dev_conf.jumbo_frame = 0.
On Tue, Jul 12, 2016 at 2:43 PM, Lu, Wenzhuo <wenzhuo.lu@intel.com> wrote:
> From: Garik E [mailto:kiragon@gmail.com]
> Sent: Tuesday, July 12, 2016 12:48 PM
> To: Lu, Wenzhuo
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] No RX frames on Intel 82599 VF
>
> Hi,
>
> On the S2600WT2 server, when DPDK is bound to VF, there is no incoming
> traffic.
> But when the same VF is bound to ixgbevf driver and configured as Linux
> interface,
> it works normally. I was able to run ping and ssh through that VF.
> So my guess is that the RX issue is not due to malfunction hardware.
>
> The same binary works correctly on S2600WTTR server with 82599 VF
> I also tested the application with Mellanox ConnectX-4 on both servers
> There were no issues with CX-4 PF and VF
>
> For some reason DPDK VF RX functionality does not work on S2600WT2.
> [Wenzhuo] No clue now. But I think you can compare what’s the difference
> between S2600WT2 and S2600WTTR.
>
>
>
> On Tue, Jul 12, 2016 at 4:24 AM, Lu, Wenzhuo <wenzhuo.lu@intel.com<mailto:
> wenzhuo.lu@intel.com>> wrote:
> Hi Garik,
>
> > -----Original Message-----
> > From: dev [mailto:dev-bounces@dpdk.org<mailto:dev-bounces@dpdk.org>] On
> Behalf Of Garik E
> > Sent: Tuesday, July 12, 2016 2:22 AM
> > To: dev@dpdk.org<mailto:dev@dpdk.org>
> > Subject: [dpdk-dev] No RX frames on Intel 82599 VF
> >
> > Hello,
> >
> >
> > I have two Intel servers S2600WTTR and S2600WT2 both with 82599 10G
> > Ethernet Controllers
> >
> > I run the same DPDK application on both servers.
> >
> > The application works with one interface bound to physical or virtual PCI
> > function depending on configuration
> >
> > The S2600WTTR server receives incoming traffic on physical and virtual
> > functions
> S2600WTTR is working right?
>
> >
> > The S2600WT2 server receives traffic only on physical function
> >
> > When I bind S2600WT2 VF to ixgbevf driver and configure it as Linux ETH
> > interface, it works normally.
> Don't understand what you're doing here. And you say *works*? Is S2600WT2
> the one not working?
>
> >
> >
> > Network sniffer shows that Ethernet frames arrive to S2600WT2 port and
> > frames are valid,
> >
> > however DPDK does not receive them.
> >
> >
> > Where can I start to debug this issue ?
> >
> >
> > OS: RHEL 6.6 x86-64
> >
> > DPDK: 16-07-rc1
>
>
prev parent reply other threads:[~2017-04-19 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 18:22 Garik E
2016-07-12 1:24 ` Lu, Wenzhuo
2016-07-12 4:48 ` Garik E
2016-07-12 6:04 ` Garik E
2016-07-12 6:43 ` Lu, Wenzhuo
2017-04-19 9:49 ` Bill Bonaparte [this message]
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=CAO8FX+SZhN9NY1aq4euJAN1fLb24rgQMfy+6D6QcAFRPkgo7mA@mail.gmail.com \
--to=programme110@gmail.com \
--cc=dev@dpdk.org \
--cc=kiragon@gmail.com \
--cc=wenzhuo.lu@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).