From: Jens Axboe <[email protected]>
To: [email protected], [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: [PATCHSET v4 0/5] Add io_uring support for waitid
Date: Sat, 9 Sep 2023 09:11:19 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
Hi,
This adds support for IORING_OP_WAITID, which is an async variant of
the waitid(2) syscall. Rather than have a parent need to block waiting
on a child task state change, it can now simply get an async notication
when the requested state change has occured.
Patches 1..4 are purely prep patches, and should not have functional
changes. They split out parts of do_wait() into __do_wait(), so that
the prepare-to-wait and sleep parts are contained within do_wait().
Patch 5 adds io_uring support.
I wrote a few basic tests for this, which can be found in the
'waitid' branch of liburing:
https://git.kernel.dk/cgit/liburing/log/?h=waitid
Also spun a custom kernel for someone to test it, and no issues reported
so far.
The code can also be found here:
https://git.kernel.dk/cgit/linux/log/?h=io_uring-waitid
include/linux/io_uring_types.h | 2 +
include/uapi/linux/io_uring.h | 2 +
io_uring/Makefile | 3 +-
io_uring/cancel.c | 5 +
io_uring/io_uring.c | 3 +
io_uring/opdef.c | 10 +-
io_uring/waitid.c | 372 +++++++++++++++++++++++++++++++++
io_uring/waitid.h | 15 ++
kernel/exit.c | 131 ++++++------
kernel/exit.h | 30 +++
10 files changed, 512 insertions(+), 61 deletions(-)
Changes since v3:
- Rebase on current tree
- Move it before the futex changes. Note that if you're testing this,
this means that the opcode values have changed. The liburing repo
has been rebased as a result as well, you'll want to update that too.
liburing also has update test cases.
- Fix races between cancelation and wakeup trigger. This follows a
scheme similar to the internal poll io_uring handling
--
Jens Axboe
next reply other threads:[~2023-09-09 16:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-09 15:11 Jens Axboe [this message]
2023-09-09 15:11 ` [PATCH 1/5] exit: abstract out should_wake helper for child_wait_callback() Jens Axboe
2023-09-09 15:11 ` [PATCH 2/5] exit: move core of do_wait() into helper Jens Axboe
2023-09-09 15:11 ` [PATCH 3/5] exit: add kernel_waitid_prepare() helper Jens Axboe
2023-09-09 15:11 ` [PATCH 4/5] exit: add internal include file with helpers Jens Axboe
2023-09-09 15:11 ` [PATCH 5/5] io_uring: add IORING_OP_WAITID support Jens Axboe
2023-09-12 17:06 ` [PATCHSET v4 0/5] Add io_uring support for waitid Jens Axboe
2023-09-19 14:45 ` Christian Brauner
2023-09-19 14:57 ` Jens Axboe
2023-09-20 14:54 ` 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 \
[email protected] \
[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