From: Cliff Burdick <shaklee3@gmail.com>
To: users <users@dpdk.org>
Subject: [dpdk-users] KNI Very Slow
Date: Fri, 10 Jun 2016 21:52:24 -0700 [thread overview]
Message-ID: <CA+Gp1nbgeEamSrEm2zji9M0TgDKBShzYUEONgVW6-qN+QQmrzA@mail.gmail.com> (raw)
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?
reply other threads:[~2016-06-11 4:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+Gp1nbgeEamSrEm2zji9M0TgDKBShzYUEONgVW6-qN+QQmrzA@mail.gmail.com \
--to=shaklee3@gmail.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).