From: Ferruh Yigit <ferruh.yigit@intel.com>
To: David Su <david.w.su@intel.com>, dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH] igb_uio: use non-threaded ISR
Date: Mon, 27 Feb 2017 16:15:22 +0000 [thread overview]
Message-ID: <8b3ddb7d-668a-62e0-5d50-86b796f27978@intel.com> (raw)
In-Reply-To: <1484953699-3156-1-git-send-email-david.w.su@intel.com>
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>
next prev parent reply other threads:[~2017-02-27 16:15 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 [this message]
2017-03-30 20:28 ` Thomas Monjalon
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=8b3ddb7d-668a-62e0-5d50-86b796f27978@intel.com \
--to=ferruh.yigit@intel.com \
--cc=david.w.su@intel.com \
--cc=dev@dpdk.org \
--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).