* [dpdk-users] KNI Very Slow
@ 2016-06-11 4:52 Cliff Burdick
0 siblings, 0 replies; only message in thread
From: Cliff Burdick @ 2016-06-11 4:52 UTC (permalink / raw)
To: users
Hi, I've been playing around with the sample KNI app, and for some reason
it's extremely slow to respond to pings after the application starts. I'm
starting it with:
./build/kni -c 0xf0 -n 4 -- -p 0x3 -P --config="(0,4,6),(1,5,7)"
and after it starts up, I'm able to ifconfig vEth0 with an IP without
issues. However, when I start to ping from another machine, it takes about
45 seconds of continuous pings before anything comes back. I added a couple
printfs to the kni app after rte_kni_tx_burst is called, and
after rte_kni_rx_burst. When each ping arrives, I see rte_kni_tx_burst
sending the packets to Linux. However, the printf after rte_kni_rx_burst
has a long period of time where nothing is coming out. Only after the 45
seconds does it reach some kind of "steady state" where the pings work
continuously, and the kni tx/rx are happening immediately. Has anyone seen
this behavior?
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-06-11 4:52 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-06-11 4:52 [dpdk-users] KNI Very Slow Cliff Burdick
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).