From: Jens Axboe <[email protected]>
To: Peter Zijlstra <[email protected]>
Cc: [email protected], [email protected],
[email protected], [email protected], [email protected]
Subject: Re: [PATCH 4/8] io_uring: add support for futex wake and wait
Date: Fri, 14 Jul 2023 09:10:16 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 7/14/23 9:08?AM, Peter Zijlstra wrote:
> On Fri, Jul 14, 2023 at 08:52:40AM -0600, Jens Axboe wrote:
>> Saw your series - I'll take a look. In terms of staging when we get
>> there, would it be possible to split your flags series into the bare
>> minimum and trivial, and then have that as a dependency for this series
>> and the rest of your series?
>
> I think you only really need the first three patches, and I hope those
> are the least controversial of the lot.
That's what it looks like to me, and yes those look trivial and risk
free :-)
I'll just put those at the base of my series for now, and once they are
stamped, would be great if you could then stuff them in a stable branch
that I could pull in.
> After those, I can implement the extra flags independently of the
> io_uring thing and all interfaces should just have it work.
>
> So yes :-)
That's the plan then!
--
Jens Axboe
next prev parent reply other threads:[~2023-07-14 15:10 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 [this message]
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
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 4/8] io_uring: add support for futex wake and wait Jens Axboe
2023-09-27 9:05 ` Peter Zijlstra
2023-09-27 12:05 ` Jens Axboe
2023-09-28 17:25 [PATCHSET v6] Add io_uring futex/futexv support Jens Axboe
2023-09-28 17:25 ` [PATCH 4/8] io_uring: add support for futex wake and wait 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] \
[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