Hi Anjum, Interface bound to uio driver can't be managed by kernel anymore.
Therefore you can't use OS network tools to get the interface information. When DPDK application starts, it will show uio bound interfaces in order. e.g. EAL: Invalid NUMA socket, default to 0 EAL: Probe PCI driver: net_ixgbe_vf (8086:10ed) device: 0000:06:00.0 (socket 0) EAL: Invalid NUMA socket, default to 0 EAL: Probe PCI driver: net_ixgbe_vf (8086:10ed) device: 0000:07:00.0 (socket 0) The 0000:06:00.0 device is the first interface DPDK uses and 0000:07:00.0 is the second. > Message: 4 > Date: Thu, 15 Jul 2021 17:47:30 +0800 > From: "Anjum, Sohail" <[email protected]> > To: "[email protected]" <[email protected]> > Subject: [dpdk-users] IGB_uio driver issue > Message-ID: > <cabsxamhzr5puk_uarmvgwrvjwkvqx1o5p+bzm-6yogeppmb...@mail.gmail.com> > Content-Type: text/plain; charset="UTF-8" > > Hi, everyone I am trying to run ndpi with dpdk. In order to do that I can > bind the port with igb_uio driver but when I bind the port. > lshw -c network -businfo > Command doesn't show the interface name. It can only show the PCI address. > So when I can run the dpdk command I dont know which interface to use. But > when I use the the same name with the old interface name then they show > this port is not available. > > Regards, > -- > *Regards*, > > *Sohail Anjum* > > *EECS Department.* > *National Chiao Tung University, Hsinchu, Taiwan* > > > End of users Digest, Vol 297, Issue 4 > *************************************
