From: Pavel Begunkov <asml.silence@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: io-uring@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
Conrad Meyer <conradmeyer@meta.com>,
linux-block@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v4 8/8] block: implement async write zero pages command
Date: Thu, 12 Sep 2024 17:38:36 +0100 [thread overview]
Message-ID: <c8963fae-8163-4e9d-9d9e-2284c080d564@gmail.com> (raw)
In-Reply-To: <ZuKzwSA79NtLAMcH@infradead.org>
On 9/12/24 10:26, Christoph Hellwig wrote:
> On Tue, Sep 10, 2024 at 09:10:34PM +0100, Pavel Begunkov wrote:
>> If we expect any error handling from the user space at all (we do),
>> it'll and have to be asynchronous, it's async commands and io_uring.
>> Asking the user to reissue a command in some form is normal.
>
> The point is that pretty much all other errors are fatal, while this
> is a not supported for which we have a guaranteed to work kernel
Yes, and there will be an error indicating that it's not
supported, just like it'll return an error this io_uring
commands are not supported by a given kernel.
> fallback. Kicking it off reuires a bit of work, but I'd rather have
> that in one place rather than applications that work on some hardware
> and not others.
There is nothing new in features that might be unsupported,
because of hardware or otherwise, it's giving control to the
userspace.
>> That's a shame, I agree, which is why I call it "presumably" faster,
>> but that actually gives more reasons why you might want this cmd
>> separately from write zeroes, considering the user might know
>> its hardware and the kernel doesn't try to choose which approach
>> faster.
>
> But the kernel is the right place to make that decision, even if we
> aren't very smart about it right now. Fanning that out to every
> single applications is a bad idea.
Apart that it will never happen
>> Users who know more about hw and e.g. prefer writes with 0 page as
>> per above. Users with lots of devices who care about pcie / memory
>> bandwidth, there is enough of those, they might want to do
>> something different like adjusting algorithms and throttling.
>> Better/easier testing, though of lesser importance.
>>
>> Those I made up just now on the spot, but the reporter did
>> specifically ask about some way to differentiate fallbacks.
>
> Well, an optional nofallback flag would be in line with how we do
> that. Do you have the original report to share somewhere?
Following with another flag "please do fallback", at which
point it doesn't make any sense when that can be done in
userspace.
--
Pavel Begunkov
next prev parent reply other threads:[~2024-09-12 16:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 22:57 [PATCH v4 0/8] implement async block discards and other ops via io_uring Pavel Begunkov
2024-09-06 22:57 ` [PATCH v4 1/8] io_uring/cmd: expose iowq to cmds Pavel Begunkov
2024-09-06 22:57 ` [PATCH v4 2/8] io_uring/cmd: give inline space in request " Pavel Begunkov
2024-09-06 22:57 ` [PATCH v4 3/8] filemap: introduce filemap_invalidate_pages Pavel Begunkov
2024-09-06 22:57 ` [PATCH v4 4/8] block: introduce blk_validate_byte_range() Pavel Begunkov
2024-09-10 7:55 ` Christoph Hellwig
2024-09-06 22:57 ` [PATCH v4 5/8] block: implement async discard as io_uring cmd Pavel Begunkov
2024-09-10 8:01 ` Christoph Hellwig
2024-09-10 10:58 ` Pavel Begunkov
2024-09-10 14:17 ` Christoph Hellwig
2024-09-10 20:22 ` Pavel Begunkov
2024-09-12 9:28 ` Christoph Hellwig
2024-09-06 22:57 ` [PATCH v4 6/8] block: implement async write zeroes command Pavel Begunkov
2024-09-06 22:57 ` [PATCH v4 7/8] block: add nowait flag for __blkdev_issue_zero_pages Pavel Begunkov
2024-09-06 22:57 ` [PATCH v4 8/8] block: implement async write zero pages command Pavel Begunkov
2024-09-10 8:02 ` Christoph Hellwig
2024-09-10 12:17 ` Pavel Begunkov
2024-09-10 14:20 ` Christoph Hellwig
2024-09-10 20:10 ` Pavel Begunkov
2024-09-12 9:26 ` Christoph Hellwig
2024-09-12 16:38 ` Pavel Begunkov [this message]
2024-09-08 22:25 ` [PATCH v4 0/8] implement async block discards and other ops via io_uring Jens Axboe
2024-09-09 14:51 ` Jens Axboe
2024-09-09 15:33 ` Jens Axboe
2024-09-09 15:09 ` 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=c8963fae-8163-4e9d-9d9e-2284c080d564@gmail.com \
--to=asml.silence@gmail.com \
--cc=axboe@kernel.dk \
--cc=conradmeyer@meta.com \
--cc=hch@infradead.org \
--cc=io-uring@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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