From: Jens Axboe <[email protected]>
To: Christian Brauner <[email protected]>
Cc: [email protected], [email protected],
Dave Chinner <[email protected]>
Subject: Re: [PATCH 2/3] pipe: enable handling of IOCB_NOWAIT
Date: Wed, 15 Mar 2023 08:16:19 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <20230315082321.47mw5essznhejv7z@wittgenstein>
On 3/15/23 2:23 AM, Christian Brauner wrote:
> On Tue, Mar 14, 2023 at 09:42:02AM -0600, Jens Axboe wrote:
>> In preparation for enabling FMODE_NOWAIT for pipes, ensure that the read
>> and write path handle it correctly. This includes the pipe locking,
>> page allocation for writes, and confirming pipe buffers.
>>
>> Acked-by: Dave Chinner <[email protected]>
>> Signed-off-by: Jens Axboe <[email protected]>
>> ---
>
> Looks good,
> Reviewed-by: Christian Brauner <[email protected]>
Thanks for the review, I'll add that. Are you OK with me carrying
these patches, or do you want to stage them for 6.4?
--
Jens Axboe
next prev parent reply other threads:[~2023-03-15 14:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 15:42 [PATCHSET v2 for-next 0/3] Add FMODE_NOWAIT support to pipes Jens Axboe
2023-03-14 15:42 ` [PATCH 1/3] fs: add 'nonblock' parameter to pipe_buf_confirm() and fops method Jens Axboe
2023-03-14 15:42 ` [PATCH 2/3] pipe: enable handling of IOCB_NOWAIT Jens Axboe
2023-03-15 8:23 ` Christian Brauner
2023-03-15 14:16 ` Jens Axboe [this message]
2023-03-15 15:02 ` Christian Brauner
2023-03-15 15:12 ` Jens Axboe
2023-03-15 15:16 ` Jens Axboe
2023-03-14 15:42 ` [PATCH 3/3] pipe: set FMODE_NOWAIT on pipes Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2023-03-08 3:10 [PATCHSET for-next 0/3] Add FMODE_NOWAIT support to pipes Jens Axboe
2023-03-08 3:10 ` [PATCH 2/3] pipe: enable handling of IOCB_NOWAIT Jens Axboe
2023-03-14 9:26 ` Christian Brauner
2023-03-14 12:03 ` Jens Axboe
2023-03-14 9:38 ` Matthew Wilcox
2023-03-14 12:04 ` 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] \
/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