From: Bart Van Assche <bvanassche@acm.org>
To: Damien Le Moal <dlemoal@kernel.org>, Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH RFC] Submit split bios in order
Date: Fri, 9 May 2025 06:46:20 -0700 [thread overview]
Message-ID: <a6b2d2bd-42ea-4bdf-80f4-299b28cc54de@acm.org> (raw)
In-Reply-To: <aa288ae2-e9db-462f-993c-9079a9a0ffad@kernel.org>
On 5/8/25 6:15 PM, Damien Le Moal wrote:
> On 5/9/25 9:42 AM, Bart Van Assche wrote:
>> If a bio is split, the bio fragments are added in reverse LBA order into
>> the plug list. This triggers write errors with zoned storage and
>> sequential writes. Fix this by preserving the LBA order when inserting in
>> the plug list.
>
> Preserving the order of the fragment would be a good thing for all block
> devices. But what I fail to see here is how this lack of ordering affects zoned
> block device writes since zone write plugging will split large BIOs when a
> write BIO goes through zone write plugging. That happens before we have a
> request, so we should never endup needing to split a zone write request.
Hi Damien,
From a comment in source file block/blk-zoned.c:
"We always receive BIOs after they are split and ready to be issued."
Does this mean that splitting bios happens before these are passed to
the code in block/blk-zoned.c?
Note: as you probably know Christoph's patch series "don't reorder
requests passed to ->queue_rqs" affects bio splitting. The bio splitting
code pushes bio fragments onto the plug list in decreasing LBA order.
Before that patch series the requests pushed onto the plug list last
were processed first and hence bio fragments are submitted in LBA order.
Since that patch series the requests pushed onto the plug list first are
processed first and hence bio fragments are submitted in decreasing LBA
order.
See also
https://lore.kernel.org/linux-block/20241113152050.157179-1-hch@lst.de/.
Thanks,
Bart.
prev parent reply other threads:[~2025-05-09 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 0:42 [PATCH RFC] Submit split bios in order Bart Van Assche
2025-05-09 1:15 ` Damien Le Moal
2025-05-09 13:46 ` Bart Van Assche [this message]
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=a6b2d2bd-42ea-4bdf-80f4-299b28cc54de@acm.org \
--to=bvanassche@acm.org \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=hch@lst.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.