From: Damien Le Moal <dlemoal@kernel.org>
To: Hannes Reinecke <hare@suse.de>, Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org
Subject: Re: [PATCH] null_blk: Always split BIOs to respect queue limits
Date: Fri, 26 Jan 2024 16:09:11 +0900 [thread overview]
Message-ID: <89fcb470-2e21-43a3-a428-000e1c6ab706@kernel.org> (raw)
In-Reply-To: <84dce2ee-5d71-47a4-b114-3ca69b3c31fb@suse.de>
On 1/26/24 16:05, Hannes Reinecke wrote:
> On 1/26/24 01:50, Damien Le Moal wrote:
>> The function null_submit_bio() used for null_blk devices configured
>> with a BIO-based queue never splits BIOs according to the queue limits
>> set with the various module and configfs parameters that the user can
>> specify.
>>
>> Add a call to bio_split_to_limits() to correctly handle large
>> BIOs that need splitting. Doing so also fixes issues with zoned devices
>> as a large BIO may cross over a zone boundary, which breaks null_blk
>> zone emulation.
>>
> That feels so wrong. Why would we need to apply queue limits to a bio?
> (Yes, I know why. We still shouldn't be doing it.)
Splitting is at least needed for zoned devices. Otherwise, everything breaks
with the zone emulation.
> Maybe indeed time to kill the bio-based path.
I have nothing against that :)
>
> But until that happens:
>
> Reviewed-by: Hannes Reinecke <hare@suse.de>
>
> Cheers,
>
> Hannes
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2024-01-26 7:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-26 0:50 [PATCH] null_blk: Always split BIOs to respect queue limits Damien Le Moal
2024-01-26 7:05 ` Hannes Reinecke
2024-01-26 7:09 ` Damien Le Moal [this message]
2024-01-26 8:37 ` Chaitanya Kulkarni
2024-01-26 14:27 ` Christoph Hellwig
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=89fcb470-2e21-43a3-a428-000e1c6ab706@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.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