From: Damien Le Moal <dlemoal@kernel.org>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
virtualization@lists.linux.dev, linux-nvme@lists.infradead.org,
linux-scsi@vger.kernel.org, linux-btrfs@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH 3/5] block: remove support for the host aware zone model
Date: Mon, 18 Dec 2023 18:48:43 +0900 [thread overview]
Message-ID: <09f1adfe-90b5-445c-b7f6-ae4fc7a9666a@kernel.org> (raw)
In-Reply-To: <20231217165359.604246-4-hch@lst.de>
On 2023/12/18 1:53, Christoph Hellwig wrote:
> When zones were first added the SCSI and ATA specs, two different
> models were supported (in addition to the drive managed one that
> is invisible to the host):
>
> - host managed where non-conventional zones there is strict requirement
> to write at the write pointer, or else an error is returned
> - host aware where a write point is maintained if writes always happen
> at it, otherwise it is left in an under-defined state and the
> sequential write preferred zones behave like conventional zones
> (probably very badly performing ones, though)
>
> Not surprisingly this lukewarm model didn't prove to be very useful and
> was finally removed from the ZBC and SBC specs (NVMe never implemented
> it). Due to to the easily disappearing write pointer host software
> could never rely on the write pointer to actually be useful for say
> recovery.
>
> Fortunately only a few HDD prototypes shipped using this model which
> never made it to mass production. Drop the support before it is too
> late. Note that any such host aware prototype HDD can still be used
> with Linux as we'll now treat it as a conventional HDD.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
[...]
> diff --git a/drivers/scsi/scsi_debug.c b/drivers/scsi/scsi_debug.c
> index 6d8218a4412264..d03d66f1149301 100644
> --- a/drivers/scsi/scsi_debug.c
> +++ b/drivers/scsi/scsi_debug.c
> @@ -339,7 +339,7 @@ struct sdebug_dev_info {
> bool used;
>
> /* For ZBC devices */
> - enum blk_zoned_model zmodel;
> + bool zoned;
> unsigned int zcap;
> unsigned int zsize;
> unsigned int zsize_shift;
> @@ -844,8 +844,11 @@ static bool write_since_sync;
> static bool sdebug_statistics = DEF_STATISTICS;
> static bool sdebug_wp;
> static bool sdebug_allow_restart;
> -/* Following enum: 0: no zbc, def; 1: host aware; 2: host managed */
> -static enum blk_zoned_model sdeb_zbc_model = BLK_ZONED_NONE;
> +static enum {
> + BLK_ZONED_NONE = 0,
> + BLK_ZONED_HA = 1,
> + BLK_ZONED_HM = 2,
> +} sdeb_zbc_model = BLK_ZONED_NONE;
> static char *sdeb_zbc_model_s;
>
> enum sam_lun_addr_method {SAM_LUN_AM_PERIPHERAL = 0x0,
> @@ -1815,8 +1818,6 @@ static int inquiry_vpd_b1(struct sdebug_dev_info *devip, unsigned char *arr)
> arr[1] = 1; /* non rotating medium (e.g. solid state) */
> arr[2] = 0;
> arr[3] = 5; /* less than 1.8" */
> - if (devip->zmodel == BLK_ZONED_HA)
> - arr[4] = 1 << 4; /* zoned field = 01b */
I think we should keep everything related to HA in scsi debug as that is an easy
way to test the block layer and scsi. no ?
Other than this, very nice cleanup !
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2023-12-18 9:48 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 16:53 remove support for the host aware zoned model Christoph Hellwig
2023-12-17 16:53 ` [PATCH 1/5] virtio_blk: cleanup zoned device probing Christoph Hellwig
2023-12-18 9:35 ` Damien Le Moal
2023-12-18 15:13 ` Stefan Hajnoczi
2024-01-16 19:02 ` [f2fs-dev] " patchwork-bot+f2fs
2023-12-17 16:53 ` [PATCH 2/5] virtio_blk: remove the broken zone revalidation support Christoph Hellwig
2023-12-18 9:37 ` Damien Le Moal
2023-12-18 15:15 ` Stefan Hajnoczi
2023-12-17 16:53 ` [PATCH 3/5] block: remove support for the host aware zone model Christoph Hellwig
2023-12-18 6:15 ` Ed Tsai (蔡宗軒)
2023-12-18 6:53 ` Damien Le Moal
2023-12-18 8:21 ` Ed Tsai (蔡宗軒)
2023-12-18 9:33 ` Damien Le Moal
2023-12-19 7:16 ` Naohiro Aota
2023-12-19 8:08 ` Ed Tsai (蔡宗軒)
2023-12-19 8:12 ` Damien Le Moal
2023-12-19 10:38 ` hch
2023-12-19 12:16 ` hch
2023-12-18 9:48 ` Damien Le Moal [this message]
2023-12-18 14:33 ` Christoph Hellwig
2023-12-17 16:53 ` [PATCH 4/5] block: simplify disk_set_zoned Christoph Hellwig
2023-12-18 9:50 ` Damien Le Moal
2023-12-17 16:53 ` [PATCH 5/5] sd: only call disk_clear_zoned when needed Christoph Hellwig
2023-12-18 9:51 ` Damien Le Moal
2023-12-19 2:16 ` remove support for the host aware zoned model Martin K. Petersen
2023-12-20 3:18 ` 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=09f1adfe-90b5-445c-b7f6-ae4fc7a9666a@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=dm-devel@lists.linux.dev \
--cc=hch@lst.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=pbonzini@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtualization@lists.linux.dev \
/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