All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org
Subject: [PATCHSET v3 0/3] Add support for registered waits
Date: Fri, 25 Oct 2024 08:12:57 -0600	[thread overview]
Message-ID: <20241025141403.169518-1-axboe@kernel.dk> (raw)

Hi,

v3 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  |  41 +++++++++++++
 io_uring/io_uring.c            | 105 ++++++++++++++++++++++++++-------
 io_uring/register.c            |  82 +++++++++++++++++++++++++
 io_uring/register.h            |   1 +
 5 files changed, 217 insertions(+), 22 deletions(-)

Since v2:
- Wrap registration with a setup struct, to better future proof the
  feature. That would allow doing a registered wait variant with the
  sigmask embedded as well, should that be interesting in the future.
- Update liburing reg-wait branch with the new registration API
- Fixup copy for 32 vs 64-bit
- Minor cleanups and comments

-- 
Jens Axboe


             reply	other threads:[~2024-10-25 14:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-25 14:12 Jens Axboe [this message]
2024-10-25 14:12 ` [PATCH 1/3] io_uring: switch struct ext_arg from __kernel_timespec to timespec64 Jens Axboe
2024-10-25 14:12 ` [PATCH 2/3] io_uring: change io_get_ext_arg() to use uaccess begin + end Jens Axboe
2024-10-25 14:13 ` [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=20241025141403.169518-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.