Re: regarding KNI

Hi C R,

This is a limitation of the KNI example and not of the DPDK package. The
current KNI example can use one core for single task - Egress/Ingress on
one port.

You definitely can change it, look into *main_loop *function.

Regards,
Daniel Kaminsky


On Thu, Jan 2, 2014 at 11:32 AM, cr singh [off-list ref] wrote:

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