On 6/21/2017 4:24 PM, Stephen Hemminger wrote: > On Wed, 21 Jun 2017 12:06:51 +0100 > Ferruh Yigit <ferruh.yi...@intel.com> wrote: > >> To have the support corresponding kernel module (UNCI) needs to be >> inserted. If kernel module is not there, application will run as >> it is without kernel control path support. >> >> When UNCI module inserted, running application creates a virtual Linux >> network interface (dpdk$) per DPDK port. This interface can be used by >> traditional Linux tools. >> >> If Userspace Network Control Interface (UNCI) kernel module >> (rte_unci.ko) inserted, virtual interfaces created for each DPDK port >> for control purposes. >> >> Created interfaces are named as dpdk#, like: >> >> $ ifconfig dpdk0; ifconfig dpdk1 >> dpdk0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 >> ether 90:e2:ba:0e:49:b9 txqueuelen 1000 (Ethernet) >> RX packets 0 bytes 0 (0.0 B) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 0 bytes 0 (0.0 B) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 >> >> dpdk1: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 >> ether 00:1b:21:76:fa:21 txqueuelen 1000 (Ethernet) >> RX packets 0 bytes 0 (0.0 B) >> RX errors 0 dropped 0 overruns 0 frame 0 >> TX packets 0 bytes 0 (0.0 B) >> TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 > > > If you get the sysfs network links correct, then udev should be able to > generate peristent network names.
I didn't get this one, currently interface names are requested from userspace via IFLA_IFNAME, as dpdk# .