From: Damien Le Moal <damien.lemoal@wdc.com>
To: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Cc: Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>,
Keith Busch <keith.busch@wdc.com>
Subject: [PATCH v2 0/2] block: add zone write granularity limit
Date: Tue, 19 Jan 2021 22:17:21 +0900 [thread overview]
Message-ID: <20210119131723.1637853-1-damien.lemoal@wdc.com> (raw)
(resending as I forgot to add nvme and scsi lists and their
maintainers. My apologies for the noise)
The first patch in this series introduces the zone write granularity
queue limit to indicate the alignment constraint for write operations
into sequential zones of zoned block devices.
The second patch fixes adds the missing documentation for
zone_append_max_bytes to the sysfs block documentation.
Changes form v1:
* Fixed typo in patch 2
Damien Le Moal (2):
block: introduce zone_write_granularity limit
block: document zone_append_max_bytes attribute
Documentation/block/queue-sysfs.rst | 13 +++++++++++++
block/blk-settings.c | 28 ++++++++++++++++++++++++++++
block/blk-sysfs.c | 7 +++++++
drivers/nvme/host/zns.c | 1 +
drivers/scsi/sd_zbc.c | 10 ++++++++++
include/linux/blkdev.h | 3 +++
6 files changed, 62 insertions(+)
--
2.29.2
next reply other threads:[~2021-01-19 14:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 13:17 Damien Le Moal [this message]
2021-01-19 13:17 ` [PATCH v2 1/2] block: introduce zone_write_granularity limit Damien Le Moal
2021-01-20 10:10 ` Christoph Hellwig
2021-01-20 11:00 ` Damien Le Moal
2021-01-20 12:36 ` Christoph Hellwig
2021-01-19 13:17 ` [PATCH v2 2/2] block: document zone_append_max_bytes attribute Damien Le Moal
2021-01-20 10:10 ` Christoph Hellwig
2021-01-20 10:07 ` [PATCH v2 0/2] block: add zone write granularity limit Christoph Hellwig
2021-01-20 10:42 ` Damien Le Moal
2021-01-20 10:46 ` Damien Le Moal
-- strict thread matches above, loose matches on Subject: below --
2021-01-19 9:38 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=20210119131723.1637853-1-damien.lemoal@wdc.com \
--to=damien.lemoal@wdc.com \
--cc=axboe@kernel.dk \
--cc=chaitanya.kulkarni@wdc.com \
--cc=hch@lst.de \
--cc=keith.busch@wdc.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.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).