All of lore.kernel.org
 help / color / mirror / Atom feed
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 v3 0/3] block: add zone write granularity limit
Date: Fri, 22 Jan 2021 17:00:11 +0900	[thread overview]
Message-ID: <20210122080014.174391-1-damien.lemoal@wdc.com> (raw)

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.

The third patch switch zonefs to use this new limit as the file block
size instead of using the physical block size.

Changes from v2:
* Added patch 3 for zonefs
* Addressed Christoph's comments on patch 1 and added the limit
  initialization for zoned nullblk

Changes from v1:
* Fixed typo in patch 2

Damien Le Moal (3):
  block: introduce zone_write_granularity limit
  block: document zone_append_max_bytes attribute
  zonefs: use zone write granularity as block size

 Documentation/block/queue-sysfs.rst | 13 ++++++++++
 block/blk-settings.c                | 39 +++++++++++++++++++++++++----
 block/blk-sysfs.c                   |  8 ++++++
 drivers/block/null_blk/zoned.c      |  1 +
 drivers/nvme/host/zns.c             |  1 +
 drivers/scsi/sd_zbc.c               | 10 ++++++++
 fs/zonefs/super.c                   |  9 +++----
 include/linux/blkdev.h              | 15 +++++++++++
 8 files changed, 86 insertions(+), 10 deletions(-)

-- 
2.29.2


WARNING: multiple messages have this Message-ID (diff)
From: Damien Le Moal <damien.lemoal@wdc.com>
To: linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Cc: linux-scsi@vger.kernel.org, Keith Busch <keith.busch@wdc.com>,
	Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
	linux-nvme@lists.infradead.org,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@lst.de>
Subject: [PATCH v3 0/3] block: add zone write granularity limit
Date: Fri, 22 Jan 2021 17:00:11 +0900	[thread overview]
Message-ID: <20210122080014.174391-1-damien.lemoal@wdc.com> (raw)

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.

The third patch switch zonefs to use this new limit as the file block
size instead of using the physical block size.

Changes from v2:
* Added patch 3 for zonefs
* Addressed Christoph's comments on patch 1 and added the limit
  initialization for zoned nullblk

Changes from v1:
* Fixed typo in patch 2

Damien Le Moal (3):
  block: introduce zone_write_granularity limit
  block: document zone_append_max_bytes attribute
  zonefs: use zone write granularity as block size

 Documentation/block/queue-sysfs.rst | 13 ++++++++++
 block/blk-settings.c                | 39 +++++++++++++++++++++++++----
 block/blk-sysfs.c                   |  8 ++++++
 drivers/block/null_blk/zoned.c      |  1 +
 drivers/nvme/host/zns.c             |  1 +
 drivers/scsi/sd_zbc.c               | 10 ++++++++
 fs/zonefs/super.c                   |  9 +++----
 include/linux/blkdev.h              | 15 +++++++++++
 8 files changed, 86 insertions(+), 10 deletions(-)

-- 
2.29.2


_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

             reply	other threads:[~2021-01-22  8:01 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-22  8:00 Damien Le Moal [this message]
2021-01-22  8:00 ` [PATCH v3 0/3] block: add zone write granularity limit Damien Le Moal
2021-01-22  8:00 ` [PATCH v3 1/3] block: introduce zone_write_granularity limit Damien Le Moal
2021-01-22  8:00   ` Damien Le Moal
2021-01-22  8:42   ` Christoph Hellwig
2021-01-22  8:42     ` Christoph Hellwig
2021-01-22  8:56     ` Damien Le Moal
2021-01-22  8:56       ` Damien Le Moal
2021-01-24 10:07       ` Christoph Hellwig
2021-01-24 10:07         ` Christoph Hellwig
2021-01-25  5:32         ` Damien Le Moal
2021-01-25  5:32           ` Damien Le Moal
2021-01-25  5:34           ` Damien Le Moal
2021-01-25  5:34             ` Damien Le Moal
2021-01-23  2:43   ` Martin K. Petersen
2021-01-23  2:43     ` Martin K. Petersen
2021-01-22  8:00 ` [PATCH v3 2/3] block: document zone_append_max_bytes attribute Damien Le Moal
2021-01-22  8:00   ` Damien Le Moal
2021-01-23  2:43   ` Martin K. Petersen
2021-01-23  2:43     ` Martin K. Petersen
2021-01-23  3:03   ` Chaitanya Kulkarni
2021-01-23  3:03     ` Chaitanya Kulkarni
2021-01-22  8:00 ` [PATCH v3 3/3] zonefs: use zone write granularity as block size Damien Le Moal
2021-01-22  8:00   ` Damien Le Moal
2021-01-22  8:42   ` Christoph Hellwig
2021-01-22  8:42     ` Christoph Hellwig
2021-01-23  2:44   ` Martin K. Petersen
2021-01-23  2:44     ` 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=20210122080014.174391-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 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.