From: Garik E <kiragon@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] No RX frames on Intel 82599 VF
Date: Mon, 11 Jul 2016 21:22:29 +0300 [thread overview]
Message-ID: <CAJuSJTCu5oPVGEWC0KeeDgcJCSsBSN2ymCY0zUDzfUNgrPwAGQ@mail.gmail.com> (raw)
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
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.
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
next reply other threads:[~2016-07-11 18:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 18:22 Garik E [this message]
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
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=CAJuSJTCu5oPVGEWC0KeeDgcJCSsBSN2ymCY0zUDzfUNgrPwAGQ@mail.gmail.com \
--to=kiragon@gmail.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).