From: Bart Van Assche <bvanassche@acm.org>
To: "Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Hannes Reinecke <hare@suse.de>,
Shaun Tancheff <shaun.tancheff@seagate.com>,
Douglas Gilbert <dgilbert@interlog.com>,
linux-scsi@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>
Subject: [PATCH v2 0/9] Support zoned devices with gap zones
Date: Thu, 21 Apr 2022 11:30:14 -0700 [thread overview]
Message-ID: <20220421183023.3462291-1-bvanassche@acm.org> (raw)
Hi Martin,
In ZBC-2 support has been improved for zones with a size that is not a power
of two by allowing host-managed devices to report gap zones. This patch adds
support for zoned devices for which data zones and gap zones alternate if the
distance between zone start LBAs is a power of two.
Please consider this patch series for kernel v5.19.
Thanks,
Bart.
Changes compared to v1:
- Made this patch series compatible with the zone querying code in BTRFS.
- Addressed Damien's off-list review comments.
- Added patch "Return early in sd_zbc_check_zoned_characteristics()" to this
series.
Bart Van Assche (9):
scsi: sd_zbc: Improve source code documentation
scsi: sd_zbc: Verify that the zone size is a power of two
scsi: sd_zbc: Use logical blocks as unit when querying zones
scsi: sd_zbc: Introduce struct zoned_disk_info
scsi: sd_zbc: Return early in sd_zbc_check_zoned_characteristics()
scsi: sd_zbc: Hide gap zones
scsi_debug: Fix a typo
scsi_debug: Rename zone type constants
scsi_debug: Add gap zone support
drivers/scsi/scsi_debug.c | 149 ++++++++++++++++++------
drivers/scsi/sd.h | 32 ++++--
drivers/scsi/sd_zbc.c | 236 +++++++++++++++++++++++++++++---------
include/scsi/scsi_proto.h | 9 +-
4 files changed, 331 insertions(+), 95 deletions(-)
next reply other threads:[~2022-04-21 18:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-21 18:30 Bart Van Assche [this message]
2022-04-21 18:30 ` [PATCH v2 1/9] scsi: sd_zbc: Improve source code documentation Bart Van Assche
2022-04-21 20:03 ` Himanshu Madhani
2022-04-21 18:30 ` [PATCH v2 2/9] scsi: sd_zbc: Verify that the zone size is a power of two Bart Van Assche
2022-04-21 20:05 ` Himanshu Madhani
2022-04-21 18:30 ` [PATCH v2 3/9] scsi: sd_zbc: Use logical blocks as unit when querying zones Bart Van Assche
2022-04-21 20:09 ` Himanshu Madhani
2022-04-21 18:30 ` [PATCH v2 4/9] scsi: sd_zbc: Introduce struct zoned_disk_info Bart Van Assche
2022-04-21 20:13 ` Himanshu Madhani
2022-04-21 18:30 ` [PATCH v2 5/9] scsi: sd_zbc: Return early in sd_zbc_check_zoned_characteristics() Bart Van Assche
2022-04-21 20:15 ` Himanshu Madhani
2022-04-21 18:30 ` [PATCH v2 6/9] scsi: sd_zbc: Hide gap zones Bart Van Assche
2022-04-21 18:30 ` [PATCH v2 7/9] scsi_debug: Fix a typo Bart Van Assche
2022-04-21 20:16 ` Himanshu Madhani
2022-04-21 18:30 ` [PATCH v2 8/9] scsi_debug: Rename zone type constants Bart Van Assche
2022-04-21 18:30 ` [PATCH v2 9/9] scsi_debug: Add gap zone support Bart Van Assche
2022-04-26 1:56 ` [PATCH v2 0/9] Support zoned devices with gap zones Douglas Gilbert
2022-04-26 2:56 ` Martin K. Petersen
2022-05-03 0:51 ` Martin K. Petersen
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=20220421183023.3462291-1-bvanassche@acm.org \
--to=bvanassche@acm.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=dgilbert@interlog.com \
--cc=hare@suse.de \
--cc=jaegeuk@kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=shaun.tancheff@seagate.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).