From: William Tu <u9012063@gmail.com>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: dpdk-dev <dev@dpdk.org>,
Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>,
Dmitry Malloy <dmitrym@microsoft.com>,
Pallavi Kadam <pallavi.kadam@intel.com>,
Ranjit Menon <ranjit.menon@intel.com>
Subject: Re: [dpdk-dev] [kmods PATCH] windows/netuio: add interrupt support
Date: Tue, 12 Oct 2021 11:46:19 -0700 [thread overview]
Message-ID: <CALDO+SbKOnouG7dg-C7=dhXa14pFu5COgPHkSKJbdX4FpmhJkg@mail.gmail.com> (raw)
In-Reply-To: <20211012011107.431188-1-dmitry.kozliuk@gmail.com>
On Mon, Oct 11, 2021 at 6:11 PM Dmitry Kozlyuk <dmitry.kozliuk@gmail.com> wrote:
>
> Add IOCTL for interrupt event delivery to user space.
>
> * IOCTL_NETUIO_INTR_CONTROL:
> Enable/disable the delivery of interrupt events.
> This is a software switch to ignore received interrupts.
> Programming the HW to stop issuing interrupts is up to the user.
>
> * IOCTL_NETUIO_INTR_QUERY:
> Wait for an interrupt event on the specified vector.
> More than one outstanding request may be issued for the same vector.
> This can be used to balance the interrupt servicing if the requests
> are issued using distinct handles waited by different threads.
> If N identical requests are issued using the same handle,
> one request will be completed each time the interrupt is triggered.
>
> MSI-X support is advertised for the driver, but the implementation
> works with any type of interrupts assigned by the kernel.
>
> Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
> ---
Hi Dmitry,
Is there a corresponding userspace code so I can give it a try?
s.t like sending IOCTL_NETUIO_INTR_CONTROL to enable a device's interrupt,
and blocked at IOCTL_NETUIO_INTR_QUERY for incoming request in the intr_queue.
Thanks
William
next prev parent reply other threads:[~2021-10-12 18:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 1:11 Dmitry Kozlyuk
2021-10-12 18:46 ` William Tu [this message]
2022-01-11 14:31 ` Dmitry Kozlyuk
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='CALDO+SbKOnouG7dg-C7=dhXa14pFu5COgPHkSKJbdX4FpmhJkg@mail.gmail.com' \
--to=u9012063@gmail.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
/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).