DPDK usage discussions
 help / color / mirror / Atom feed
From: Budiský Jakub <ibudisky@fit.vutbr.cz>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Interrupt mode, queues, own event loop
Date: Sat, 05 Sep 2020 23:21:06 +0200
Message-ID: <db580197366c29c228e3b4b72b703b34@fit.vutbr.cz> (raw)
In-Reply-To: <20200904091827.59056b16@hermes.lan>

On 2020-09-04 18:18, Stephen Hemminger wrote:
> The per-queue interrupt functionality for PCI devices is built
> on top of MSI-X interrupts. The uio_pci_generic driver you are using
> does not support MSI-X.
> 
> The way UIO driver works is to use the legacy INTx functionality,
> and when an interrupt occurs the device driver in the kernel is called.
> For the uio_pci_generic driver this is mapped to the device file 
> descriptor.
> 
> For VFIO, you can have one interrupt per queue and it uses eventfd's
> to create a per-queue channel.

Hi,

thanks for the valuable info!

I've now switched to the `vfio` module even for testing and I can 
confirm I get a set of separate eventfd file descriptors. I've 
encountered a new issue though that appears like a bug to me.

Either one of the file descriptors (`--vfio-intr msix`, always the one 
associated with the last queue, regardless of the initialization order) 
or all of them (`--vfio-intr msi`) are available for reading just once 
per application run. I cannot get any followup interrupts and I can 
confirm by polling that there are new packets that have arrived.

With `--vfio-intr legacy` I get a same file descriptor for all my 
workers but it is also only triggered once.

As far as I understand there is no clear flag for the MSI(-X) interrupts 
and so I'm not sure what else to try. There is nothing of interest in 
the application output (not even with `--log-level lib.eal:debug`).

Thanks again.

Best regards,
Jakub Budisky

  reply	other threads:[~2020-09-05 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04 10:24 Budiský Jakub
2020-09-04 16:18 ` Stephen Hemminger
2020-09-05 21:21   ` Budiský Jakub [this message]
2020-09-08 15:09     ` Budiský Jakub

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=db580197366c29c228e3b4b72b703b34@fit.vutbr.cz \
    --to=ibudisky@fit.vutbr.cz \
    --cc=stephen@networkplumber.org \
    --cc=users@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

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git