From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: David Su <david.w.su@intel.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH] igb_uio: use non-threaded ISR
Date: Thu, 30 Mar 2017 22:28:41 +0200 [thread overview]
Message-ID: <1601764.nrObFx1ngS@xps13> (raw)
In-Reply-To: <8b3ddb7d-668a-62e0-5d50-86b796f27978@intel.com>
2017-02-27 16:15, Ferruh Yigit:
> On 1/20/2017 11:08 PM, David Su wrote:
> > This eliminates the overhead of a task switch when an interrupt arrives.
> >
> > Signed-off-by: David Su <david.w.su@intel.com>
>
> Overall I agree with Stephen to switch vfio when possible but for the
> cases igb_uio still required:
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
Applied, thanks
prev parent reply other threads:[~2017-03-30 20:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-20 23:08 David Su
2017-01-20 23:50 ` Stephen Hemminger
2017-01-23 19:20 ` Su, David W
2017-01-23 21:12 ` Stephen Hemminger
2017-02-24 17:54 ` Ferruh Yigit
2017-02-25 0:21 ` Su, David W
2017-02-27 16:15 ` Ferruh Yigit
2017-03-30 20:28 ` 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=1601764.nrObFx1ngS@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=david.w.su@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stephen@networkplumber.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).