From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Subject: [PATCHSET v2 0/3] Add support for registered waits
Date: Wed, 23 Oct 2024 09:54:31 -0600 [thread overview]
Message-ID: <20241023155639.1124650-1-axboe@kernel.dk> (raw)
Hi,
v2 of the registered wait support, avoiding needless copies for doing
high frequency waits. For v1, see the posting here:
https://lore.kernel.org/io-uring/20241022204708.1025470-1-axboe@kernel.dk/T/#m2d1eb2cc648b9f9c292fd75fc6bc2a8d71eadd49
As with v1, find the kernel repo here:
https://git.kernel.dk/cgit/linux/log/?h=io_uring-reg-wait
and the liburing side here:
https://git.kernel.dk/cgit/liburing/log/?h=reg-wait
include/linux/io_uring_types.h | 10 ++++
include/uapi/linux/io_uring.h | 18 ++++++
io_uring/io_uring.c | 104 ++++++++++++++++++++++++++-------
io_uring/register.c | 79 +++++++++++++++++++++++++
io_uring/register.h | 1 +
5 files changed, 190 insertions(+), 22 deletions(-)
Since v1:
- Add io_unregister_cqwait_reg() for ring exit cleanp
- Ensure some 32-bit archs work with uaccess
- Add separate index for checking validity of wait index
- Add various sanity checking for registration
- Account memory for cqwait region
- Expand the test cases in liburing quite a bit
--
Jens Axboe
next reply other threads:[~2024-10-23 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 15:54 Jens Axboe [this message]
2024-10-23 15:54 ` [PATCH 1/3] io_uring: switch struct ext_arg from __kernel_timespec to timespec64 Jens Axboe
2024-10-23 15:54 ` [PATCH 2/3] io_uring: change io_get_ext_arg() to use uaccess begin + end Jens Axboe
2024-10-23 15:54 ` [PATCH 3/3] io_uring: add support for fixed wait regions Jens Axboe
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=20241023155639.1124650-1-axboe@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.