From: Niklas Cassel <cassel@kernel.org>
To: Stefan Hajnoczi <stefanha@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Cc: Sam Li <faithilikerun@gmail.com>,
Damien Le Moal <dlemoal@kernel.org>,
Niklas Cassel <cassel@kernel.org>,
qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: [PATCH v6 02/15] virtio-blk: do not merge requests across a zone boundary
Date: Mon, 21 Sep 2026 16:28:04 +0200 [thread overview]
Message-ID: <20260921142819.2916043-3-cassel@kernel.org> (raw)
In-Reply-To: <20260921142819.2916043-1-cassel@kernel.org>
From: Sam Li <faithilikerun@gmail.com>
virtio_blk_submit_multireq() fuses adjacent in-zone requests into a
single request. On a zoned backend, a merged zone append request
that straddles a zone boundary is rejected by the device because
each write/read must stay within a single zone (virtio 1.4, 5.2.6.1).
Add a bail condition to the merge coalescer: if combining the
candidate request into the current batch would cross a zone
boundary, flush the current batch and start a new one.
Signed-off-by: Sam Li <faithilikerun@gmail.com>
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Reviewed-by: Niklas Cassel <cassel@kernel.org>
Signed-off-by: Niklas Cassel <cassel@kernel.org>
---
block/block-backend.c | 11 +++++++++++
hw/block/virtio-blk.c | 22 +++++++++++++++++++++-
include/system/block-backend-io.h | 1 +
3 files changed, 33 insertions(+), 1 deletion(-)
diff --git a/block/block-backend.c b/block/block-backend.c
index 37ba7e9fc4..049e70ddcb 100644
--- a/block/block-backend.c
+++ b/block/block-backend.c
@@ -2326,6 +2326,17 @@ uint32_t blk_get_request_alignment(BlockBackend *blk)
return bs ? bs->bl.request_alignment : BDRV_SECTOR_SIZE;
}
+/*
+ * Returns the zone size in bytes for a zoned backend, or 0 if @blk does
+ * not present zoned geometry.
+ */
+uint64_t blk_get_zone_size(BlockBackend *blk)
+{
+ BlockDriverState *bs = blk_bs(blk);
+ IO_CODE();
+ return bs ? bs->bl.zone_size : 0;
+}
+
/* Returns the optimal write zeroes alignment, in bytes; guaranteed nonzero */
uint32_t blk_get_pwrite_zeroes_alignment(BlockBackend *blk)
{
diff --git a/hw/block/virtio-blk.c b/hw/block/virtio-blk.c
index 61c341ce2c..1b93364b24 100644
--- a/hw/block/virtio-blk.c
+++ b/hw/block/virtio-blk.c
@@ -288,6 +288,9 @@ static void virtio_blk_submit_multireq(VirtIOBlock *s, MultiReqBuffer *mrb)
int i = 0, start = 0, num_reqs = 0, niov = 0, nb_sectors = 0;
uint32_t max_transfer;
int64_t sector_num = 0;
+ uint64_t zone_size = blk_get_zone_size(s->blk);
+ bool zone_cross;
+ int64_t zone_nr_sectors, end_sector;
if (mrb->num_reqs == 1) {
submit_requests(s, mrb, 0, 1, -1);
@@ -303,17 +306,34 @@ static void virtio_blk_submit_multireq(VirtIOBlock *s, MultiReqBuffer *mrb)
for (i = 0; i < mrb->num_reqs; i++) {
VirtIOBlockReq *req = mrb->reqs[i];
if (num_reqs > 0) {
+ /*
+ * On zoned backends, a single backend write/read must not span
+ * a zone boundary. Bail out of merging if combining req into
+ * the current batch would straddle a zone.
+ */
+ if (zone_size > 0) {
+ zone_nr_sectors = zone_size / BDRV_SECTOR_SIZE;
+ end_sector = req->sector_num
+ + req->qiov.size / BDRV_SECTOR_SIZE - 1;
+ zone_cross = (sector_num / zone_nr_sectors) !=
+ (end_sector / zone_nr_sectors);
+ } else {
+ zone_cross = false;
+ }
+
/*
* NOTE: We cannot merge the requests in below situations:
* 1. requests are not sequential
* 2. merge would exceed maximum number of IOVs
* 3. merge would exceed maximum transfer length of backend device
+ * 4. merge would cross a zone boundary on a zoned backend
*/
if (sector_num + nb_sectors != req->sector_num ||
niov > blk_get_max_iov(s->blk) - req->qiov.niov ||
req->qiov.size > max_transfer ||
nb_sectors > (max_transfer -
- req->qiov.size) / BDRV_SECTOR_SIZE) {
+ req->qiov.size) / BDRV_SECTOR_SIZE ||
+ zone_cross) {
submit_requests(s, mrb, start, num_reqs, niov);
num_reqs = 0;
}
diff --git a/include/system/block-backend-io.h b/include/system/block-backend-io.h
index fd84723d9d..78d410b8df 100644
--- a/include/system/block-backend-io.h
+++ b/include/system/block-backend-io.h
@@ -121,6 +121,7 @@ uint32_t blk_get_request_alignment(BlockBackend *blk);
uint32_t blk_get_pwrite_zeroes_alignment(BlockBackend *blk);
uint32_t blk_get_max_transfer(BlockBackend *blk);
uint64_t blk_get_max_hw_transfer(BlockBackend *blk);
+uint64_t blk_get_zone_size(BlockBackend *blk);
int coroutine_fn blk_co_copy_range(BlockBackend *blk_in, int64_t off_in,
BlockBackend *blk_out, int64_t off_out,
--
2.55.0
next prev parent reply other threads:[~2026-09-21 14:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 14:28 [PATCH v6 00/15] block: fix the zone write granularity and the zone append limit Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 01/15] block: widen BlockLimits.zone_size to uint64_t Niklas Cassel
2026-09-21 14:28 ` Niklas Cassel [this message]
2026-09-21 14:28 ` [PATCH v6 03/15] block: add a helper for the index of the zone an offset falls in Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 04/15] block: add a helper to check if a zone is conventional Niklas Cassel
2026-09-22 18:55 ` Stefan Hajnoczi
2026-09-21 14:28 ` [PATCH v6 05/15] hw/block: derive the zone write granularity from the block sizes Niklas Cassel
2026-09-22 18:58 ` Stefan Hajnoczi
2026-09-21 14:28 ` [PATCH v6 06/15] virtio-blk: check the write granularity of writes to sequential zones Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 07/15] hw/block: reject a zoned device that the block sizes cannot address Niklas Cassel
2026-09-22 19:01 ` Stefan Hajnoczi
2026-09-21 14:28 ` [PATCH v6 08/15] block: reject zone appends that are not a multiple of the sector size Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 09/15] block: reject a zone append that is larger than a zone Niklas Cassel
2026-09-22 19:04 ` Stefan Hajnoczi
2026-09-21 14:28 ` [PATCH v6 10/15] file-posix: remove the zone append write granularity check Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 11/15] virtio-blk: add a max-append-sectors property Niklas Cassel
2026-09-22 19:14 ` Stefan Hajnoczi
2026-09-21 14:28 ` [PATCH v6 12/15] block: remove BlockLimits.max_append_sectors Niklas Cassel
2026-09-22 19:16 ` Stefan Hajnoczi
2026-09-21 14:28 ` [PATCH v6 13/15] file-posix: reject a zone append past the device capacity Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 14/15] file-posix: reject a zone append to a full or conventional zone Niklas Cassel
2026-09-21 14:28 ` [PATCH v6 15/15] block: do not use CoroutineIOCompletion to hold a return value Niklas Cassel
2026-10-06 13:15 ` [PATCH v6 00/15] block: fix the zone write granularity and the zone append limit Niklas Cassel
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=20260921142819.2916043-3-cassel@kernel.org \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=faithilikerun@gmail.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
/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.