All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Stefan Hajnoczi <stefanha@redhat.com>,
	Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@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 12/15] block: remove BlockLimits.max_append_sectors
Date: Mon, 21 Sep 2026 16:28:14 +0200	[thread overview]
Message-ID: <20260921142819.2916043-13-cassel@kernel.org> (raw)
In-Reply-To: <20260921142819.2916043-1-cassel@kernel.org>

The field described the largest zone append that a backend accepts. It
had one writer and one reader, and neither is left.

file-posix filled it from the zone_append_max_bytes queue attribute,
which bounds REQ_OP_ZONE_APPEND, an operation it never issues: Linux has
no userspace interface for one, so raw_co_zone_append() substitutes the
write pointer of the zone for the offset and the request reaches the
host as a plain pwritev().

The transfer limit does not apply either, no more than it does to an
ordinary write. This driver reports max_hw_transfer but never sets
BlockLimits.max_transfer, which is what bdrv_aligned_pwritev() splits
by, so a request of any size goes to the host kernel whole and is split
there: on a null_blk device whose zone_append_max_bytes is 130560, a
16 MiB append completes and advances the write pointer by 16 MiB. That
is safe for a sequential zone, as Linux issues the fragments of a split
write in order, with zone write plugging since 6.10 and zone write
locking before that.

virtio-blk was the reader, and now takes what it reports to a guest from
a property instead.

Remove the field and the assignment that filled it. Keeping it would be
worse than not having it: a driver that set it, believing something
enforced it, would be silently ignored.

Signed-off-by: Niklas Cassel <cassel@kernel.org>
---
 block/file-posix.c               | 5 -----
 include/block/block_int-common.h | 3 ---
 2 files changed, 8 deletions(-)

diff --git a/block/file-posix.c b/block/file-posix.c
index c1ac49d23d..1a4ca9d942 100644
--- a/block/file-posix.c
+++ b/block/file-posix.c
@@ -1488,11 +1488,6 @@ static void raw_refresh_zoned_limits(BlockDriverState *bs, struct stat *st,
     }
     bs->bl.nr_zones = ret;
 
-    ret = get_sysfs_long_val(st, "zone_append_max_bytes");
-    if (ret > 0) {
-        bs->bl.max_append_sectors = ret >> BDRV_SECTOR_BITS;
-    }
-
     ret = get_sysfs_long_val(st, "zone_write_granularity");
     if (ret >= 0) {
         bs->bl.write_granularity = ret;
diff --git a/include/block/block_int-common.h b/include/block/block_int-common.h
index 7abd2b12bb..cfc7b0f427 100644
--- a/include/block/block_int-common.h
+++ b/include/block/block_int-common.h
@@ -913,9 +913,6 @@ typedef struct BlockLimits {
     /* total number of zones */
     uint32_t nr_zones;
 
-    /* maximum sectors of a zone append write operation */
-    uint32_t max_append_sectors;
-
     /* maximum number of open zones */
     uint32_t max_open_zones;
 
-- 
2.55.0



  parent reply	other threads:[~2026-09-21 14:31 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 ` [PATCH v6 02/15] virtio-blk: do not merge requests across a zone boundary Niklas Cassel
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 ` Niklas Cassel [this message]
2026-09-22 19:16   ` [PATCH v6 12/15] block: remove BlockLimits.max_append_sectors 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-13-cassel@kernel.org \
    --to=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=faithilikerun@gmail.com \
    --cc=hreitz@redhat.com \
    --cc=kwolf@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.