From: Peter Zijlstra <[email protected]>
To: Jens Axboe <[email protected]>
Cc: [email protected], [email protected],
[email protected], [email protected], [email protected]
Subject: Re: [PATCH 8/8] io_uring: add support for vectored futex waits
Date: Thu, 13 Jul 2023 13:54:12 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Wed, Jul 12, 2023 at 10:20:17AM -0600, Jens Axboe wrote:
> int io_futex_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe);
> +int io_futexv_prep(struct io_kiocb *req, const struct io_uring_sqe *sqe);
> int io_futex_wait(struct io_kiocb *req, unsigned int issue_flags);
> +int io_futex_waitv(struct io_kiocb *req, unsigned int issue_flags);
> int io_futex_wake(struct io_kiocb *req, unsigned int issue_flags);
That's an inconsistent naming convention.. I'll stare at the rest later.
next prev parent reply other threads:[~2023-07-13 11:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 16:20 [PATCHSET v2 0/8] Add io_uring futex/futexv support Jens Axboe
2023-07-12 16:20 ` [PATCH 1/8] futex: abstract out futex_op_to_flags() helper Jens Axboe
2023-07-12 16:20 ` [PATCH 2/8] futex: factor out the futex wake handling Jens Axboe
2023-07-12 16:20 ` [PATCH 3/8] futex: abstract out a __futex_wake_mark() helper Jens Axboe
2023-07-12 16:20 ` [PATCH 4/8] io_uring: add support for futex wake and wait Jens Axboe
2023-07-13 11:15 ` Peter Zijlstra
2023-07-13 16:25 ` Jens Axboe
2023-07-13 17:24 ` Peter Zijlstra
2023-07-14 14:52 ` Jens Axboe
2023-07-14 15:08 ` Peter Zijlstra
2023-07-14 15:10 ` Jens Axboe
2023-07-12 16:20 ` [PATCH 5/8] futex: add wake_data to struct futex_q Jens Axboe
2023-07-12 16:20 ` [PATCH 6/8] futex: make futex_parse_waitv() available as a helper Jens Axboe
2023-07-12 16:20 ` [PATCH 7/8] futex: make the vectored futex operations available Jens Axboe
2023-07-12 16:20 ` [PATCH 8/8] io_uring: add support for vectored futex waits Jens Axboe
2023-07-13 11:54 ` Peter Zijlstra [this message]
2023-07-13 16:26 ` Jens Axboe
2023-07-12 16:58 ` [PATCHSET v2 0/8] Add io_uring futex/futexv support Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2023-09-21 18:29 [PATCHSET v5] " Jens Axboe
2023-09-21 18:29 ` [PATCH 8/8] io_uring: add support for vectored futex waits Jens Axboe
2023-09-26 6:41 ` Jens Axboe
2023-09-26 15:25 ` Jens Axboe
2023-09-28 17:25 [PATCHSET v6] Add io_uring futex/futexv support Jens Axboe
2023-09-28 17:25 ` [PATCH 8/8] io_uring: add support for vectored futex waits 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=20230713115412.GI3138667@hirez.programming.kicks-ass.net \
[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