[dpdk-dev] problem in running KNI application
Hi Devs, I am trying to run KNI application on my system (whose lstopo result is attached herewith) , basically i am unable to insert correct --config="(port,lcore_rx,lcore_tx[,lcore_kthread,...])" option while running it. I am getting this [root at localhost DPDK-1.5.0]# ./examples/kni/build/kni -c 0x3 -n 2 -- -P -p 0x3 --config="(0,2,4,0),(1,1,3,0)" EAL: Cannot read numa node link for lcore 0 - using physical package id instead EAL: Detected lcore 0 as core 0 on socket 0 EAL: Cannot read numa node link for lcore 1 - using physical package id instead EAL: Detected lcore 1 as core 1 on socket 0 EAL: Setting up hugepage memory... EAL: cannot open /proc/self/numa_maps, consider that all memory is in socket_id 0 EAL: Ask a virtual area of 0x398458880 bytes EAL: Virtual area found at 0x9e80 (size = 0x17c0) EAL: Ask a virtual area of 0x20971520 bytes EAL: Virtual area found at 0x9d00 (size = 0x140) EAL: Ask a virtual area of 0x8388608 bytes EAL: Virtual area found at 0x9c40 (size = 0x80) EAL: Requesting 102 pages of size 4MB from socket 0 EAL: TSC frequency is ~2893448 KHz EAL: Master core 0 is ready (tid=b7741800) EAL: Core 1 is ready (tid=b6e44b40) APP: Port ID: 0 APP: Rx lcore ID: 2, Tx lcore ID: 4 APP: Kernel thread lcore ID: 0 APP: Port ID: 1 APP: Rx lcore ID: 1, Tx lcore ID: 3 APP: Kernel thread lcore ID: 0 EAL: Error - exiting with code: 1 Cause: lcore id 2 for port 0 receiving not enabled can anybody please explain me the details of the --config option in kni application Thanks in advance -- cr singh
[dpdk-dev] Fwd: problem in running KNI application
Hi Devs, I am trying to run KNI application on my system (whose lstopo result is attached herewith) , basically i am unable to insert correct --config="(port,lcore_rx,lcore_tx[,lcore_kthread,...])" option while running it. I am getting this [root at localhost DPDK-1.5.0]# ./examples/kni/build/kni -c 0x3 -n 2 -- -P -p 0x3 --config="(0,2,4,0),(1,1,3,0)" EAL: Cannot read numa node link for lcore 0 - using physical package id instead EAL: Detected lcore 0 as core 0 on socket 0 EAL: Cannot read numa node link for lcore 1 - using physical package id instead EAL: Detected lcore 1 as core 1 on socket 0 EAL: Setting up hugepage memory... EAL: cannot open /proc/self/numa_maps, consider that all memory is in socket_id 0 EAL: Ask a virtual area of 0x398458880 bytes EAL: Virtual area found at 0x9e80 (size = 0x17c0) EAL: Ask a virtual area of 0x20971520 bytes EAL: Virtual area found at 0x9d00 (size = 0x140) EAL: Ask a virtual area of 0x8388608 bytes EAL: Virtual area found at 0x9c40 (size = 0x80) EAL: Requesting 102 pages of size 4MB from socket 0 EAL: TSC frequency is ~2893448 KHz EAL: Master core 0 is ready (tid=b7741800) EAL: Core 1 is ready (tid=b6e44b40) APP: Port ID: 0 APP: Rx lcore ID: 2, Tx lcore ID: 4 APP: Kernel thread lcore ID: 0 APP: Port ID: 1 APP: Rx lcore ID: 1, Tx lcore ID: 3 APP: Kernel thread lcore ID: 0 EAL: Error - exiting with code: 1 Cause: lcore id 2 for port 0 receiving not enabled can anybody please explain me the details of the --config option in kni application Thanks in advance -- cr singh
[dpdk-dev] regarding KNI
hello devs, I am using DPDK 1.5.0 and trying to use KNI interface to measure throughput through it I have machine with 2 lcores and 2 physical interface, and in running kni sample application --config parameter we are supposed to give 1)port no, 2)lcore_rx, 3)lcore_tx, right? so can it be possible to give same lcore no. for both ports, like kni -c 0x3 -n 4 -- -P -p 0x3 --config"(0,0,1),(1,0,1)" As i have tried and after running this two interface vEth0 and vEth1 is created, but when i am giving ip with ifconfig to vEth1 then it is showing the below message ... SIOCSIFFLAGS: Timer expired, while i am able to bring up the the vEth0 interface successfully. - i am pasting some details which prints while running the application ... Checking link status .done Port 0 Link Up - speed 1000 Mbps - full-duplex Port 1 Link Up - speed 1000 Mbps - full-duplex APP: Lcore 1 is writing to port 0 APP: Lcore 0 is reading from port 0 and here in last two line Lcore 1 and Lcore 0 is writting and reading for port 0 and may be therefore i am able to bring up the vEth0. and there is no core for port 1 so it is failing. - So my question is why can't we use same lcores for reading and writing for both ports, does DPDK restricts using same lcores for 2 ports (as it seems), and if so, then why?? Thanks in advance C R
