From: Tomasz K <tomasz.kasowicz@gmail.com>
To: dev <dev@dpdk.org>
Subject: [dpdk-dev] l2fwd not working on PF while working on VF
Date: Wed, 9 Apr 2014 16:03:55 +0200 [thread overview]
Message-ID: <CAHJKsGyK2is-irtemAA9PuDS=Ut12mQt36aJJ+vwvXJafn_31g@mail.gmail.com> (raw)
Dear All
I have a setup with Intel 82576 DPDK NIC.
For one of the available DPDK ports i have created 8 VFs using igb_uio
based on steps presented in programmers guide. Some of them are attached to
VM, some maybe used on host
After some tests with l2fwd application i found out that it is not working
for PF, but works perfectly for any VF (both on host and in VM).
I'm still trying to find root cause of this issue but maybe someone
encountered such problem
Thanks in advance
Tomasz Kasowicz
Setup:
Intel(R) Xeon(R) CPU E31220 @ 3.10GHz running Ubuntu 12.04 LTS
pci_unbind.py --status
Network devices using IGB_UIO driver
====================================
0000:01:00.1 '82576NS Gigabit Network Connection' drv=igb_uio unused=igb
0000:02:11.1 '82576 Virtual Function' drv=igb_uio unused=igbvf
Network devices using kernel driver
===================================
0000:00:19.0 '82579LM Gigabit Network Connection' if=eth1 drv=e1000e
unused= *Active*
0000:01:00.0 '82576NS Gigabit Network Connection' if=eth0 drv=igb
unused=igb_uio *Active*
0000:02:10.1 '82576 Virtual Function' if= drv=pci-stub unused=igbvf,igb_uio
0000:02:10.3 '82576 Virtual Function' if= drv=pci-stub unused=igbvf,igb_uio
0000:02:10.5 '82576 Virtual Function' if= drv=pci-stub unused=igbvf,igb_uio
0000:02:10.7 '82576 Virtual Function' if= drv=pci-stub unused=igbvf,igb_uio
0000:02:11.3 '82576 Virtual Function' if= drv=pci-stub unused=igbvf,igb_uio
0000:02:11.5 '82576 Virtual Function' if= drv=pci-stub unused=igbvf,igb_uio
0000:02:11.7 '82576 Virtual Function' if= drv=pci-stub unused=igbvf,igb_uio
0000:04:00.0 '82574L Gigabit Network Connection' if=eth3 drv=e1000e
unused=igb_uio
Other network devices
=====================
<none>
cat /sys/bus/pci/devices/0000\:01\:00.1/max_vfs
8
ls -alrt /sys/bus/pci/devices/0000\:01\:00.1/virtfn*
lrwxrwxrwx 1 root root 0 Apr 9 12:09
/sys/bus/pci/devices/0000:01:00.1/virtfn7 -> ../0000:02:11.7
lrwxrwxrwx 1 root root 0 Apr 9 12:09
/sys/bus/pci/devices/0000:01:00.1/virtfn6 -> ../0000:02:11.5
lrwxrwxrwx 1 root root 0 Apr 9 12:09
/sys/bus/pci/devices/0000:01:00.1/virtfn5 -> ../0000:02:11.3
lrwxrwxrwx 1 root root 0 Apr 9 12:09
/sys/bus/pci/devices/0000:01:00.1/virtfn4 -> ../0000:02:11.1
lrwxrwxrwx 1 root root 0 Apr 9 12:09
/sys/bus/pci/devices/0000:01:00.1/virtfn3 -> ../0000:02:10.7
lrwxrwxrwx 1 root root 0 Apr 9 12:09
/sys/bus/pci/devices/0000:01:00.1/virtfn2 -> ../0000:02:10.5
lrwxrwxrwx 1 root root 0 Apr 9 12:09
/sys/bus/pci/devices/0000:01:00.1/virtfn1 -> ../0000:02:10.3
lrwxrwxrwx 1 root root 0 Apr 9 12:09
/sys/bus/pci/devices/0000:01:00.1/virtfn0 -> ../0000:02:10.1
next reply other threads:[~2014-04-09 14:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 14:03 Tomasz K [this message]
2014-04-09 15:10 ` Richardson, Bruce
2014-04-09 15:21 ` Tomasz K
2014-04-09 16:25 ` Chris Wright
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='CAHJKsGyK2is-irtemAA9PuDS=Ut12mQt36aJJ+vwvXJafn_31g@mail.gmail.com' \
--to=tomasz.kasowicz@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).