DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Su, David W" <david.w.su@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] igb_uio: use non-threaded ISR
Date: Mon, 23 Jan 2017 13:12:39 -0800	[thread overview]
Message-ID: <20170123131239.31547f0e@xeon-e3> (raw)
In-Reply-To: <3875C02542CA2945BF761013C1F5B8E57F3DC9AD@ORSMSX109.amr.corp.intel.com>

On Mon, 23 Jan 2017 19:20:02 +0000
"Su, David W" <david.w.su@intel.com> wrote:

> If rte_eth_conf.intr_conf.rxq != 0 and rte_eth_conf.intr_conf.lsc = 0 when rte_eth_dev_configure() is called, rx queue interrupts can be enabled/disabled with rte_eth_dev_rx_intr_{enable|disable} and DPDK applications can wait for rx queue interrupts with rte_epoll_wait().  This is the case for both igb_uio and vfio-pci drivers.
> 
> vfio-pci already uses non-threaded ISR, but currently we can only use igb_uio when running DPDK applications in virtual machines.
> 

Can't you use vfio-noiommu mode?

  reply	other threads:[~2017-01-23 21:12 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 [this message]
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

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=20170123131239.31547f0e@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=david.w.su@intel.com \
    --cc=dev@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).