[dpdk-dev] Ports not detected by IGB_UIO in DPDK 1.7.1 in QEMU_KVM environment
Manoj Viswanath
manoj.viswanath at gmail.com
Fri Nov 7 18:56:08 CET 2014
Hi Bruce,
Please find my comment in lined.
On Fri, Nov 7, 2014 at 9:00 PM, Bruce Richardson <bruce.richardson at intel.com
> wrote:
> On Fri, Nov 07, 2014 at 08:31:34PM +0530, Manoj Viswanath wrote:
> > Hi Bruce,
> >
> > I was not doing anything specific for binding the NICs to IGB_UIO (like
> > invoking "dpdk_nic_bind.py" script explicitly) when using my application
> > with DPDK 1.6.0. The e1000 devices assigned via virt-manager to the VM
> were
> > automatically getting picked up and initialized by IGB_UIO within each
> VM.
> >
> > The same is not working with DPDK 1.7.1 now.
> >
> > I tried exporting the "dpdk_nic_bind.py" script into my VM (running DPDK
> > 1.7.1) and tried to check the status. The emulated devices were shown as
> > neither bound to kernel nor to IGB_UIO as evident from below output:-
> >
> >
> <--------------------------------------------------------------------------------------------------->
> > Network devices using DPDK-compatible driver
> > ============================================
> > <none>
> >
> > Network devices using kernel driver
> > ===================================
> > 0000:00:03.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
> >
> > Other network devices
> > =====================
> > 0000:00:04.0 '82540EM Gigabit Ethernet Controller' unused=igb_uio
> > 0000:00:05.0 '82540EM Gigabit Ethernet Controller' unused=igb_uio
> >
> <--------------------------------------------------------------------------------------------------->
> >
> > When i tried to forcefully bind the NICs using the "--bind=igb_uio"
> option
>
> Was there any output of the dpdk_nic_bind script? What does the output of
> it with --status show afterwards?
>
>
[MANOJ]
Yes. Please refer below output:-
********************************************************************
Network devices using DPDK-compatible driver
============================================
0000:00:04.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=
0000:00:05.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=
Network devices using kernel driver
===================================
0000:00:03.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
Other network devices
=====================
<none>
********************************************************************
However, when i start the DPDK application, i am getting the error log as
indicated in earlier mail.
The difference with DPDK 1.6.1 is that at the same stage IGB_UIO has
already bound the assigned devices without having to explicitly run the
"dpdk_nic_bind.py". Please find below the application log when run with
DPDK 1.6.0:-
********************************************************************
Network devices using DPDK-compatible driver
============================================
0000:00:04.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=
0000:00:08.0 '82540EM Gigabit Ethernet Controller' drv=igb_uio unused=
Network devices using kernel driver
===================================
0000:00:03.0 'Virtio network device' if= drv=virtio-pci unused=igb_uio
Other network devices
=====================
<none>
********************************************************************
Kindly note that in both cases, logs have been taken after loading IGB_UIO
prior to starting DPDK application.
[/MANOJ]
Regards,
> /Bruce
>
>
Regards,
MANOJ
More information about the dev
mailing list