From: Peter Zijlstra <[email protected]>
To: Jens Axboe <[email protected]>
Cc: [email protected], [email protected],
[email protected], [email protected]
Subject: Re: [PATCHSET v6] Add io_uring futex/futexv support
Date: Fri, 29 Sep 2023 09:53:17 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Thu, Sep 28, 2023 at 11:25:09AM -0600, Jens Axboe wrote:
> include/linux/io_uring_types.h | 5 +
> include/uapi/linux/io_uring.h | 4 +
> io_uring/Makefile | 1 +
> io_uring/cancel.c | 5 +
> io_uring/cancel.h | 4 +
> io_uring/futex.c | 386 +++++++++++++++++++++++++++++++++
> io_uring/futex.h | 36 +++
> io_uring/io_uring.c | 7 +
> io_uring/opdef.c | 34 +++
> kernel/futex/futex.h | 20 ++
> kernel/futex/requeue.c | 3 +-
> kernel/futex/syscalls.c | 18 +-
> kernel/futex/waitwake.c | 49 +++--
> 13 files changed, 545 insertions(+), 27 deletions(-)
Thanks for bearing with us on the futex2 thing!
Acked-by: Peter Zijlstra (Intel) <[email protected]>
next prev parent reply other threads:[~2023-09-29 7:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-28 17:25 [PATCHSET v6] Add io_uring futex/futexv support Jens Axboe
2023-09-28 17:25 ` [PATCH 1/8] futex: move FUTEX2_VALID_MASK to futex.h Jens Axboe
2023-09-28 17:25 ` [PATCH 2/8] futex: factor out the futex wake handling Jens Axboe
2023-09-28 17:25 ` [PATCH 3/8] futex: abstract out a __futex_wake_mark() helper Jens Axboe
2023-09-28 17:25 ` [PATCH 4/8] io_uring: add support for futex wake and wait Jens Axboe
2023-09-28 17:25 ` [PATCH 5/8] futex: add wake_data to struct futex_q Jens Axboe
2023-09-28 17:25 ` [PATCH 6/8] futex: make futex_parse_waitv() available as a helper Jens Axboe
2023-09-28 17:25 ` [PATCH 7/8] futex: make the vectored futex operations available Jens Axboe
2023-09-28 17:25 ` [PATCH 8/8] io_uring: add support for vectored futex waits Jens Axboe
2023-09-29 7:53 ` Peter Zijlstra [this message]
2023-09-29 9:11 ` [PATCHSET v6] Add io_uring futex/futexv support 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=20230929075317.GA6282@noisy.programming.kicks-ass.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