From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Marc Sune <marc.sune@bisdn.de>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] Adding RTE_KNI_PREEMPT_DEFAULT configuration option
Date: Mon, 23 Feb 2015 18:53:01 +0100 [thread overview]
Message-ID: <4797646.LBczmNhxo7@xps13> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A809527@SHSMSX104.ccr.corp.intel.com>
2015-02-17 01:21, Zhang, Helin:
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Marc Sune
> > This patch introduces CONFIG_RTE_KNI_PREEMPT_DEFAULT flag. When set to
> > 'no', KNI kernel thread(s) do not call schedule_timeout_interruptible(), which
> > improves overall KNI performance at the expense of CPU cycles (polling).
> >
> > Default values is 'yes', maintaining the same behaviour as of now.
> >
> > v2: CONFIG_RTE_KNI_PREEMPT -> CONFIG_RTE_KNI_PREEMPT_DEFAULT
> >
> > Signed-off-by: Marc Sune <marc.sune@bisdn.de>
> Acked-by: Helin Zhang <helin.zhang@intel.com>
Applied, thanks
prev parent reply other threads:[~2015-02-23 17:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 14:25 Marc Sune
2015-02-17 1:21 ` Zhang, Helin
2015-02-23 17:53 ` Thomas Monjalon [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=4797646.LBczmNhxo7@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=marc.sune@bisdn.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 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).