[dpdk-dev] a NIC binding to igb_uio module of DPDK is down

[Wodkowski, PawelX]

> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of BYEONG-GI KIM
> Sent: Wednesday, August 13, 2014 06:27
> To: dev at dpdk.org; Dpdk-ovs at lists.01.org
> Subject: [dpdk-dev] a NIC binding to igb_uio module of DPDK is down
> 
> Hello.
> 
> I deployed openstack with dpdk-ovs and I'm now testing it.
> 
> The problem is that a NIC which is binding to igb_uio module of DPDK is
> physically down so that it seems not communicate with the other hosts
> through the NIC.
> 
> The test environment is as below:
> 
> OS: RHEL 6 with kernel 3.7.10
> Hardware information: Intel Atom Processor C2758, 64GB DDR3, 4x RJ45
> Gigabit Ethernet LAN ports, etc.
> DPDK version: 1.7.0
> ovdk version: 1.1
> 
> I checked the NIC's status via ./tools/dpdk_nic_bind.py --status, and it
> doesn't snow *Active* status:
> 
> ./tools/dpdk_nic_bind.py --status
> 
> Network devices using DPDK-compatible driver
> ============================================
> 0000:00:14.1 'Ethernet Connection I354' drv=igb_uio unused=igb
> 
> Network devices using kernel driver
> ===================================
> 0000:00:14.0 'Ethernet Connection I354' if=eth0 drv=igb unused=igb_uio
> *Active*
> 0000:00:14.2 'Ethernet Connection I354' if=eth2 drv=igb unused=igb_uio
> *Active*
> 0000:00:14.3 'Ethernet Connection I354' if=eth3 drv=igb unused=igb_uio
> 
> Other network devices
> =====================
> <none>
> 
> The NIC port on the PC doesn't glitter physically, which means it seems not
> connected physically.
> 
> Doesn't the processor support DPDK, or what is causing the problem?
> 
> Any comments would be really appreciated.

You should bring down interface before binding it to igb_uio so the interface 
can't be active :)
Interface is managed by DPDK app, not the system so it will
not be shown as active. Try binding '0000:00:14.3' to igb uio and run some 
example like L2 forwarding first to see if it works.
> 
> Best Regards
> 
> Byeong-Gi KIM