From: Damien Le Moal <dlemoal@kernel.org>
To: Bart Van Assche <bvanassche@acm.org>,
Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@lists.linux.dev, Mike Snitzer <snitzer@kernel.org>,
Alasdair Kergon <agk@redhat.com>
Subject: Re: [PATCH v2] dm: Preserve the order of REQ_PREFLUSH writes
Date: Fri, 12 Sep 2025 09:08:07 +0900 [thread overview]
Message-ID: <c108d8a8-ae2f-453a-9eaf-a9b30ba77910@kernel.org> (raw)
In-Reply-To: <c89d0b4a-35a8-46eb-b078-e65102a0b817@acm.org>
On 9/12/25 08:16, Bart Van Assche wrote:
>
> On 9/11/25 4:03 PM, Damien Le Moal wrote:
>> I suspect it is because this will be handled by the flush machinery during the
>> submit_bio() to the underlying device ?
>
> Indeed.
>
>> But if that is the case, why is it a problem with multiple devices ?
>> The same block layer flush machinery will handle that preflush write for all devices.
> The REQ_PREFLUSH semantics require that the REQ_PREFLUSH is submitted to
> *all* underlying devices before the data that is included in the bio is
> written, even if the data in the bio only affects a single underlying
> device.
You patch would be much better with all this explained in the commit message.
Please add the above explanation in the next version with Mikulas comments
addressed.
Of note is that this seems to apply to all devices, and not just zoned ones.
--
Damien Le Moal
Western Digital Research
prev parent reply other threads:[~2025-09-12 0:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 17:27 [PATCH v2] dm: Preserve the order of REQ_PREFLUSH writes Bart Van Assche
2025-09-11 6:01 ` Hannes Reinecke
2025-09-11 16:31 ` Bart Van Assche
2025-09-11 16:35 ` Mikulas Patocka
2025-09-12 19:56 ` [PATCH v3] dm: optimize REQ_PREFLUSH with data when using the linear target Mikulas Patocka
2025-09-12 20:51 ` Bart Van Assche
2025-09-15 15:42 ` [PATCH v4] " Mikulas Patocka
2025-09-15 15:55 ` Bart Van Assche
2025-09-18 1:54 ` Shinichiro Kawasaki
2025-09-18 11:15 ` Mikulas Patocka
2025-09-19 2:47 ` Shinichiro Kawasaki
2025-09-11 23:03 ` [PATCH v2] dm: Preserve the order of REQ_PREFLUSH writes Damien Le Moal
2025-09-11 23:16 ` Bart Van Assche
2025-09-12 0:08 ` Damien Le Moal [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=c108d8a8-ae2f-453a-9eaf-a9b30ba77910@kernel.org \
--to=dlemoal@kernel.org \
--cc=agk@redhat.com \
--cc=bvanassche@acm.org \
--cc=dm-devel@lists.linux.dev \
--cc=mpatocka@redhat.com \
--cc=snitzer@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.