From: Damien Le Moal <dlemoal@kernel.org>
To: Niklas Cassel <cassel@kernel.org>,
Stefan Hajnoczi <stefanha@redhat.com>,
Kevin Wolf <kwolf@redhat.com>, Hanna Reitz <hreitz@redhat.com>,
Fam Zheng <fam@euphon.net>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: Sam Li <faithilikerun@gmail.com>,
qemu-block@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v3 03/12] block: add a helper for the index of the zone an offset falls in
Date: Sat, 5 Sep 2026 09:32:09 +0900 [thread overview]
Message-ID: <9b7b887c-5701-4c04-8ee0-e5377535a0fa@kernel.org> (raw)
In-Reply-To: <20260904161801.1568841-4-cassel@kernel.org>
On 9/5/26 01:17, Niklas Cassel wrote:
> Deriving the zone that an offset belongs to is open coded in five places,
> in two files, as a division of the offset by BlockLimits.zone_size. The
> zone size of a zoned device is always a power of two, which Linux requires
> of every device it accepts, so the division is a shift.
>
> Add bdrv_zone_index() and use it. No functional change; the count of zones
> that a management operation spans stays a division, since it is a length
> rather than an offset.
>
> Signed-off-by: Niklas Cassel <cassel@kernel.org>
Nice cleanup! One comment below.
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
> +uint32_t bdrv_zone_index(BlockDriverState *bs, uint64_t offset)
> +{
> + IO_CODE();
> +
> + return offset >> ctz64(bs->bl.zone_size);
> +}
Should we save ctz64(bs->bl.zone_size) as bs->bl.zone_size_shift to avoid these
repeated ctz64() calls? Given how frequently this helper is used, that may be
worthwhile.
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2026-09-05 0:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 16:17 [PATCH v3 00/12] block: fix the zone write granularity and the zone append limit Niklas Cassel
2026-09-04 16:17 ` [PATCH v3 01/12] block: widen BlockLimits.zone_size to uint64_t Niklas Cassel
2026-09-04 16:17 ` [PATCH v3 02/12] virtio-blk: do not merge requests across a zone boundary Niklas Cassel
2026-09-04 16:17 ` [PATCH v3 03/12] block: add a helper for the index of the zone an offset falls in Niklas Cassel
2026-09-05 0:32 ` Damien Le Moal [this message]
2026-09-04 16:17 ` [PATCH v3 04/12] virtio-blk: report the effective zone write granularity Niklas Cassel
2026-09-04 16:17 ` [PATCH v3 05/12] virtio-blk: check the write granularity of writes to sequential zones Niklas Cassel
2026-09-05 0:33 ` Damien Le Moal
2026-09-04 16:17 ` [PATCH v3 06/12] hw/block: reject a zoned device whose write pointers are unaddressable Niklas Cassel
2026-09-05 0:34 ` Damien Le Moal
2026-09-04 16:17 ` [PATCH v3 07/12] block: reject zone appends that are not a multiple of the sector size Niklas Cassel
2026-09-04 16:17 ` [PATCH v3 08/12] file-posix: remove the zone append write granularity check Niklas Cassel
2026-09-04 16:17 ` [PATCH v3 09/12] file-posix: base the zone append limit on the transfer limit Niklas Cassel
2026-09-04 16:17 ` [PATCH v3 10/12] virtio-blk: derive the maximum zone append size Niklas Cassel
2026-09-04 16:17 ` [PATCH v3 11/12] file-posix: reject a zone append past the device capacity Niklas Cassel
2026-09-04 16:18 ` [PATCH v3 12/12] file-posix: reject a zone append to a full or conventional zone Niklas Cassel
2026-09-05 0:38 ` Damien Le Moal
2026-09-07 10:47 ` Niklas Cassel
2026-09-08 0:18 ` Damien Le Moal
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=9b7b887c-5701-4c04-8ee0-e5377535a0fa@kernel.org \
--to=dlemoal@kernel.org \
--cc=cassel@kernel.org \
--cc=faithilikerun@gmail.com \
--cc=fam@euphon.net \
--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.