From: Olivier Langlois <[email protected]>
To: Stefan Roesch <[email protected]>,
[email protected], [email protected]
Cc: [email protected], [email protected]
Subject: Re: [PATCH v9 1/4] liburing: add api to set napi busy poll settings
Date: Fri, 02 Feb 2024 11:41:46 -0500 [thread overview]
Message-ID: <d78b0ed1ca8e1ff3a394bac4ae976232486a2931.camel@olivierlanglois.net> (raw)
In-Reply-To: <[email protected]>
On Tue, 2023-04-25 at 11:20 -0700, Stefan Roesch wrote:
> +
> +int io_uring_register_napi(struct io_uring *ring, struct
> io_uring_napi *napi)
> +{
> + return __sys_io_uring_register(ring->ring_fd,
> + IORING_REGISTER_NAPI, napi, 0);
> +}
> +
> +int io_uring_unregister_napi(struct io_uring *ring, struct
> io_uring_napi *napi)
> +{
> + return __sys_io_uring_register(ring->ring_fd,
> + IORING_UNREGISTER_NAPI, napi, 0);
> +}
my apologies if this is not the latest version of the patch but I think
that it is...
nr_args should be 1 to match what __io_uring_register() in the current
corresponding kernel patch expects:
https://git.kernel.dk/cgit/linux/commit/?h=io_uring-napi&id=787d81d3132aaf4eb4a4a5f24ff949e350e537d0
next prev parent reply other threads:[~2024-02-02 16:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 18:20 [PATCH v9 0/4] liburing: add api for napi busy poll Stefan Roesch
2023-04-25 18:20 ` [PATCH v9 1/4] liburing: add api to set napi busy poll settings Stefan Roesch
2024-02-02 16:41 ` Olivier Langlois [this message]
2024-02-02 16:42 ` Jens Axboe
2024-02-02 17:41 ` Olivier Langlois
2024-02-02 17:48 ` Jens Axboe
2024-02-02 20:11 ` Olivier Langlois
2024-02-02 20:14 ` Jens Axboe
2024-02-02 20:23 ` Olivier Langlois
2024-02-02 22:20 ` Jens Axboe
2024-02-02 22:46 ` Jens Axboe
2024-02-03 2:30 ` Jens Axboe
2023-04-25 18:20 ` [PATCH v9 2/4] liburing: add documentation for new napi busy polling Stefan Roesch
2023-04-25 18:20 ` [PATCH v9 3/4] liburing: add example programs for napi busy poll Stefan Roesch
2023-04-25 18:20 ` [PATCH v9 4/4] liburing: update changelog with new feature Stefan Roesch
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=d78b0ed1ca8e1ff3a394bac4ae976232486a2931.camel@olivierlanglois.net \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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