From: Stephen Hemminger <stephen@networkplumber.org>
To: Nirmoy Das <ndas@suse.de>
Cc: ferruh.yigit@intel.com, dev@dpdk.org
Subject: Re: KNI latency improvement
Date: Fri, 29 Dec 2017 09:13:45 -0800 [thread overview]
Message-ID: <20171229091345.31022a59@xeon-e3> (raw)
In-Reply-To: <0a4ff780-55fc-7c42-e3ab-b6b22a73cfbd@suse.de>
On Fri, 29 Dec 2017 15:27:03 +0100
Nirmoy Das <ndas@suse.de> wrote:
> Hi Ferruh,
>
> There is latency in the range of milliseconds when packets are passed
> through KNI up to the IP stack. With CONFIG_RTE_KNI_PREEMPT_DEFAULT=n
> its required sacrifice a cpu core. Do you have any suggestion to improve
> latency without sacrificing a cpu?
>
> What do you think about using cond_resched() instead of
> schedule_timeout_interruptible(), in our test it helped to reduce
> latency?
>
That fully consumes a CPU core when doing KNI.
It would be better to figure out how to use a a NAPI style
API for this. I.e keep processing packet until idle,
then poll for a small window more, then if still idle
wait in kernel to be kicked by syscall from user space.
prev parent reply other threads:[~2017-12-29 17:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-29 14:27 KNI latency improvement Nirmoy Das
2017-12-29 17:13 ` Stephen Hemminger [this message]
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=20171229091345.31022a59@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ndas@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.