From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: Thomas Lazor <tjlazor@vt.edu>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK Problem Binding to Network Port
Date: Sat, 21 May 2016 00:05:21 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8973C940304@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAN5tR+4xKXV-dXifn6SAJ1X9e3=H=jTpw2dhOAYVRGFTHmt3+A@mail.gmail.com>
Hi Thomas,
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Thomas Lazor
> Sent: Friday, May 20, 2016 10:57 PM
> To: users@dpdk.org
> Subject: [dpdk-users] DPDK Problem Binding to Network Port
>
> Hi,
>
> I am running into a problem when I bind the igb_uio driver to the network
> card. I am using dpdk 16.04 and my kernel version is 3.2.14.
>
> Using the setup script, I compiled the target library, inserted the igb_uio
> module, set up hugepages, and bound the igb_uio driver.
>
> $ ./tools/dpdk_nic_bind.py --status
>
> Network devices using DPDK-compatible driver
> ============================================
> 0000:01:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection' drv=igb_uio
> unused=uio_pci_generic
>
> Network devices using kernel driver
> ===================================
> 0000:01:00.1 '82599ES 10-Gigabit SFI/SFP+ Network Connection' if=eth4
> drv=ixgbe unused=igb_uio,uio_pci_generic
> 0000:06:00.0 'I350 Gigabit Network Connection' if=eth0 drv=igb
> unused=igb_uio,uio_pci_generic *Active*
> 0000:06:00.1 'I350 Gigabit Network Connection' if=eth1 drv=igb
> unused=igb_uio,uio_pci_generic
>
> Other network devices
> =====================
> <none>
>
>
> However, when I run ifconfig -a, I can no longer see the network card:
>
> $ ifconfig -a
> eth0 Link encap:Ethernet HWaddr 00:25:90:E1:83:24
> inet addr:10.1.1.42 Bcast:10.1.1.255 Mask:255.255.255.0
> inet6 addr: fe80::225:90ff:fee1:8324/64 Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:7634 errors:0 dropped:72 overruns:0 frame:0
> TX packets:4978 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:1051991 (1.0 MiB) TX bytes:732247 (715.0 KiB)
> Memory:dfd20000-dfd40000
>
> eth1 Link encap:Ethernet HWaddr 00:25:90:E1:83:25
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
> Memory:dfd00000-dfd20000
>
> eth4 Link encap:Ethernet HWaddr 00:1B:21:A6:15:A1
> BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> inet6 addr: ::1/128 Scope:Host
> UP LOOPBACK RUNNING MTU:16436 Metric:1
> RX packets:54 errors:0 dropped:0 overruns:0 frame:0
> TX packets:54 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:3552 (3.4 KiB) TX bytes:3552 (3.4 KiB)
>
> mic0 Link encap:Ethernet HWaddr 4C:79:BA:30:01:59
> inet addr:172.31.1.254 Bcast:172.31.1.255 Mask:255.255.255.0
> inet6 addr: fe80::4e79:baff:fe30:159/64 Scope:Link
> UP BROADCAST RUNNING MTU:64512 Metric:1
> RX packets:0 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
>
> Why is this? I believe I should see a dpdk0 card when it is bound. When I
> unbind the card, it does show up if I run ifconfig.
Ifconfig only shows the devices that are bound to a kernel driver.
In your case, you are binding a device to igb_uio, so the kernel has no visibility of it anymore.
Once you bind the device to igb_uio, you can run a DPDK application and use that port in it.
Pablo
>
> Many thanks,
>
> Thomas
prev parent reply other threads:[~2016-05-21 0:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-20 21:57 Thomas Lazor
2016-05-21 0:05 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D8973C940304@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=tjlazor@vt.edu \
--cc=users@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).