From: Damien Le Moal <dlemoal@kernel.org>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: Mike Snitzer <snitzer@kernel.org>,
Mikulas Patocka <mpatocka@redhat.com>,
linux-block@vger.kernel.org, dm-devel@lists.linux.dev
Subject: Re: [PATCH 2/3] block: add a REQ_ZWPLUG_UNORDERED flag
Date: Wed, 19 Nov 2025 12:17:30 +0900 [thread overview]
Message-ID: <624d4ad1-3d30-433d-80c3-ecc3cc6cca46@kernel.org> (raw)
In-Reply-To: <20251118070321.2367097-3-hch@lst.de>
On 11/18/25 16:03, Christoph Hellwig wrote:
> This instructs the zone write plugging code to queue up any bio not
> at the write pointer, and includes an implicit guarantee that the caller
> will fill any sector gaps. I.e., this can be used by file systems and
> stacking block drivers, but not for untrusted user block device writes.
>
> Because all writes through the write plug cancel all outstanding writes
> for the plug there is no risk that queue up writes for higher sectors are
> stuck in the zone write plug even on error.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Looks good.
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2025-11-19 3:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 7:03 add a flag to allow underordered zoned writes Christoph Hellwig
2025-11-18 7:03 ` [PATCH 1/3] block: add a bio_list_add_sorted helper Christoph Hellwig
2025-11-19 3:09 ` Damien Le Moal
2025-11-18 7:03 ` [PATCH 2/3] block: add a REQ_ZWPLUG_UNORDERED flag Christoph Hellwig
2025-11-19 3:17 ` Damien Le Moal [this message]
2025-11-18 7:03 ` [PATCH 3/3] dm-kcopyd: use REQ_ZWPLUG_UNORDERED Christoph Hellwig
2025-11-19 3:18 ` Damien Le Moal
2025-11-19 6:10 ` add a flag to allow underordered zoned writes Bart Van Assche
2025-11-19 7:58 ` Christoph Hellwig
2025-11-19 17:00 ` 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=624d4ad1-3d30-433d-80c3-ecc3cc6cca46@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--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.