[dpdk-dev] Interface once added to DPDK goes missing from ifconfig

2015-06-29 Thread Keunhong Lee
To fully utilize DPDK's performance, it is recommended to use native userspace drivers. Because userspace drivers do not interact with your kernel, it is trivial not having 'interfaces' for your kernel. YES you are bypassing whole kernel, if you are using userspace drivers. You may need KNI when:

[dpdk-dev] Interface once added to DPDK goes missing from ifconfig

2015-06-29 Thread Keunhong Lee
DPDK's igb_uio driver does not generate 'netdev' interfaces, so you cannot see any interface via ifconfig. (However, they are registered as 'rte_eth_dev' in your DPDK application.) You'd better to use KNI drivers to have 'netdev' intefaces. Keunhong. 2015-06-29 8:51 GMT+09:00 Abhishek Verma :

[dpdk-dev] Interface once added to DPDK goes missing from ifconfig

2015-06-29 Thread Abhishek Verma
Hi Keunhong, Thanks for the response. I was reading about KNI ( http://dpdk.org/doc/guides/sample_app_ug/kernel_nic_interface.html), and that seems to defeat the purpose of DPDK -- the whole point of using DPDK was to bypass the kernel. Now, when i implement KNI, then packets emanating from the D

[dpdk-dev] Interface once added to DPDK goes missing from ifconfig

2015-06-29 Thread Abhishek Verma
Hi, I have three ethernet interfaces in my VirtualBox as shown below: root at VirtualBox:/home/akabra/dpdk/dpdk-2.0.0/tools# ifconfig eth1 Link encap:Ethernet HWaddr 08:00:27:3f:34:56 inet addr:192.168.0.123 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::a00:27ff:fe3