Linux block layer
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: Damien Le Moal <dlemoal@kernel.org>, Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org
Cc: Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v3 04/13] block: remember a zone type regardless of its condition
Date: Tue, 11 Aug 2026 13:29:28 +0200	[thread overview]
Message-ID: <bdd4007b-690f-45e8-afee-067cef5649e8@suse.de> (raw)
In-Reply-To: <20260811105852.1245357-5-dlemoal@kernel.org>

On 8/11/26 12:58 PM, Damien Le Moal wrote:
> Currently, bdev_zone_is_seq() identifies a sequential zone by looking at
> the zone condition, assuming that any zone that does not have the
> condition BLK_ZONE_COND_NOT_WP is a sequential write required zone. That
> is correct only as long as the target zoned device does not support
> storage element depopulation (aka HDD head depopulation), which is a
> feature that can transition conventional zones to the read-only or offline
> condition. For such device, we cannot distinguish anymore between
> conventional and sequential zones using the zone condition as both zone
> types can have the same conditions.
> 
> Prepare for fully supporting storage element depopulation and restoration
> by caching the type of a zone in addition to its condition. This is
> implemented by reformating the zones_cond array using a more compact zone
> condition representation with the new enum blk_zstate. This zone condition
> representation only uses the lower 4 bits of a byte for the condition
> values, thus leaving the high order 4 bits of each byte entry of the
> array for flags. The flag BLK_ZFLAG_CONV is defined to indicate
> conventional zones.
> 
> The helper functions blk_zstate_to_zone_cond() and
> blk_zone_cond_to_zstate() are implemented using lookup tables to convert
> between enum blk_zone_condition values and enum blk_zstate zone condition
> values. The helper blk_zstate_set() can be used to prepare a zones_state
> entry for a disk with a zone condition and zone type flags. This helper is
> used in disk_zone_set_cond() to update a zone condition.
> bdev_zone_is_seq() is modified to use the flags of the zones_state array
> entries to identify sequential zones. The zones_state array initialization
> and revalidation is unchanged from the former zones_cond array.
> 
> Overall, any zone condition that is being considered outside of the
> zones_state array always uses the enum blk_zone_condition values as
> before, thus minimizing the number of changes.
> 
> Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
> Reviewed-by: Bart Van Assche <bvanassche@acm.org>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
> ---
>   block/blk-zoned.c      | 202 +++++++++++++++++++++++++++++------------
>   include/linux/blkdev.h |   2 +-
>   2 files changed, 143 insertions(+), 61 deletions(-)
> 
Reviewed-by: Hannes Reinecke <hare@kernel.org>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                  Kernel Storage Architect
hare@suse.de                                +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich

  reply	other threads:[~2026-08-11 11:29 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-11 10:58 [PATCH v3 00/13] Improve handling of offline and read-only zones Damien Le Moal
2026-08-11 10:58 ` [PATCH v3 01/13] block: remove disk_free_zone_resources() Damien Le Moal
2026-08-11 11:41   ` Johannes Thumshirn
2026-08-11 10:58 ` [PATCH v3 02/13] block: refactor disk_revalidate_zone_resources() Damien Le Moal
2026-08-11 11:46   ` Johannes Thumshirn
2026-08-11 10:58 ` [PATCH v3 03/13] block: refactor disk_update_zone_resources() Damien Le Moal
2026-08-11 11:28   ` Hannes Reinecke
2026-08-11 11:48   ` Johannes Thumshirn
2026-08-11 10:58 ` [PATCH v3 04/13] block: remember a zone type regardless of its condition Damien Le Moal
2026-08-11 11:29   ` Hannes Reinecke [this message]
2026-08-11 10:58 ` [PATCH v3 05/13] block: refactor bdev_zone_is_seq() Damien Le Moal
2026-08-11 11:30   ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 06/13] block: introduce disk_for_all_zone_wplugs() Damien Le Moal
2026-08-11 11:31   ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 07/13] block: drop all zone write plugs on capacity changes Damien Le Moal
2026-08-11 11:33   ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 08/13] block: propagate readonly and offline conditions to zone write plugs Damien Le Moal
2026-08-11 11:35   ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 09/13] block: always treat offline and read-only zones as dead Damien Le Moal
2026-08-11 11:36   ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 10/13] block: fail zone management operations to read-only and offline zones Damien Le Moal
2026-08-11 11:41   ` Hannes Reinecke
2026-08-11 12:13     ` Damien Le Moal
2026-08-11 12:16       ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 11/13] block: allow read-only and offline conventional zones Damien Le Moal
2026-08-11 11:43   ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 12/13] block: simplify disk_zone_set_cond() Damien Le Moal
2026-08-11 11:45   ` Hannes Reinecke
2026-08-11 10:58 ` [PATCH v3 13/13] block: flag zoned disks with GENHD_FL_NO_PART Damien Le Moal
2026-08-11 11:45   ` Hannes Reinecke

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=bdd4007b-690f-45e8-afee-067cef5649e8@suse.de \
    --to=hare@suse.de \
    --cc=axboe@kernel.dk \
    --cc=dlemoal@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-block@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox