All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Damien Le Moal <damien.lemoal@wdc.com>, linux-block@vger.kernel.org
Cc: 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>,
	Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>
Subject: Re: [PATCH v4 0/8] block: add zone write granularity limit
Date: Wed, 10 Feb 2021 07:45:12 -0700	[thread overview]
Message-ID: <cfe15751-e07e-101f-49d8-a2f184e30618@kernel.dk> (raw)
In-Reply-To: <20210128044733.503606-1-damien.lemoal@wdc.com>

On 1/27/21 9:47 PM, Damien Le Moal wrote:
> The first patch of this series adds missing documentation of the
> zone_append_max_bytes sysfs attribute.
> 
> The following 3 patches are cleanup and preparatory patches for the
> introduction of the zone write granularity limit. The goal of these
> patches is to have all code setting a device queue zoned model to use
> the helper function blk_queue_set_zoned(). The nvme driver, null_blk
> driver and the partition code are modified to do so.
> 
> The fourth 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. This limit is always set
> by default to the device logical block size. The following patch
> documents this new limit.
> 
> The last 2 patches introduce the blk_queue_clear_zone_settings()
> function and modify the SCSI sd driver to clear the zone related queue
> limits and resources of a host-aware zoned disk that is changed to a
> regular disk due to the presence of partitions.

Applied, thanks.

-- 
Jens Axboe


WARNING: multiple messages have this Message-ID (diff)
From: Jens Axboe <axboe@kernel.dk>
To: Damien Le Moal <damien.lemoal@wdc.com>, linux-block@vger.kernel.org
Cc: Keith Busch <keith.busch@wdc.com>,
	Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>,
	linux-nvme@lists.infradead.org, linux-scsi@vger.kernel.org,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v4 0/8] block: add zone write granularity limit
Date: Wed, 10 Feb 2021 07:45:12 -0700	[thread overview]
Message-ID: <cfe15751-e07e-101f-49d8-a2f184e30618@kernel.dk> (raw)
In-Reply-To: <20210128044733.503606-1-damien.lemoal@wdc.com>

On 1/27/21 9:47 PM, Damien Le Moal wrote:
> The first patch of this series adds missing documentation of the
> zone_append_max_bytes sysfs attribute.
> 
> The following 3 patches are cleanup and preparatory patches for the
> introduction of the zone write granularity limit. The goal of these
> patches is to have all code setting a device queue zoned model to use
> the helper function blk_queue_set_zoned(). The nvme driver, null_blk
> driver and the partition code are modified to do so.
> 
> The fourth 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. This limit is always set
> by default to the device logical block size. The following patch
> documents this new limit.
> 
> The last 2 patches introduce the blk_queue_clear_zone_settings()
> function and modify the SCSI sd driver to clear the zone related queue
> limits and resources of a host-aware zoned disk that is changed to a
> regular disk due to the presence of partitions.

Applied, thanks.

-- 
Jens Axboe


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

  parent reply	other threads:[~2021-02-10 14:45 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28  4:47 [PATCH v4 0/8] block: add zone write granularity limit Damien Le Moal
2021-01-28  4:47 ` Damien Le Moal
2021-01-28  4:47 ` [PATCH v4 1/8] block: document zone_append_max_bytes attribute Damien Le Moal
2021-01-28  4:47   ` Damien Le Moal
2021-01-28 10:20   ` Johannes Thumshirn
2021-01-28 10:20     ` Johannes Thumshirn
2021-01-28  4:47 ` [PATCH v4 2/8] nvme: cleanup zone information initialization Damien Le Moal
2021-01-28  4:47   ` Damien Le Moal
2021-01-28  9:17   ` Christoph Hellwig
2021-01-28  9:17     ` Christoph Hellwig
2021-01-28  9:27     ` Damien Le Moal
2021-01-28  9:27       ` Damien Le Moal
2021-01-28  9:32       ` Christoph Hellwig
2021-01-28  9:32         ` Christoph Hellwig
2021-01-28  4:47 ` [PATCH v4 3/8] nullb: use blk_queue_set_zoned() to setup zoned devices Damien Le Moal
2021-01-28  4:47   ` Damien Le Moal
2021-01-28  5:12   ` Chaitanya Kulkarni
2021-01-28  5:12     ` Chaitanya Kulkarni
2021-01-28  9:17   ` Christoph Hellwig
2021-01-28  9:17     ` Christoph Hellwig
2021-01-28 11:17   ` Johannes Thumshirn
2021-01-28 11:17     ` Johannes Thumshirn
2021-01-28  4:47 ` [PATCH v4 4/8] block: use blk_queue_set_zoned in add_partition() Damien Le Moal
2021-01-28  4:47   ` Damien Le Moal
2021-01-28  5:16   ` Chaitanya Kulkarni
2021-01-28  5:16     ` Chaitanya Kulkarni
2021-01-28  9:17   ` Christoph Hellwig
2021-01-28  9:17     ` Christoph Hellwig
2021-01-28 11:28   ` Johannes Thumshirn
2021-01-28 11:28     ` Johannes Thumshirn
2021-01-28  4:47 ` [PATCH v4 5/8] block: introduce zone_write_granularity limit Damien Le Moal
2021-01-28  4:47   ` Damien Le Moal
2021-01-28  9:19   ` Christoph Hellwig
2021-01-28  9:19     ` Christoph Hellwig
2021-01-28 11:32   ` Johannes Thumshirn
2021-01-28 11:32     ` Johannes Thumshirn
2021-02-05  2:54   ` Martin K. Petersen
2021-02-05  2:54     ` Martin K. Petersen
2021-01-28  4:47 ` [PATCH v4 6/8] zonefs: use zone write granularity as block size Damien Le Moal
2021-01-28  4:47   ` Damien Le Moal
2021-01-28  5:17   ` Chaitanya Kulkarni
2021-01-28  5:17     ` Chaitanya Kulkarni
2021-01-28 11:33   ` Johannes Thumshirn
2021-01-28 11:33     ` Johannes Thumshirn
2021-01-28  4:47 ` [PATCH v4 7/8] block: introduce blk_queue_clear_zone_settings() Damien Le Moal
2021-01-28  4:47   ` Damien Le Moal
2021-01-28  5:26   ` Chaitanya Kulkarni
2021-01-28  5:26     ` Chaitanya Kulkarni
2021-01-28  9:21   ` Christoph Hellwig
2021-01-28  9:21     ` Christoph Hellwig
2021-01-28  9:32     ` Damien Le Moal
2021-01-28  9:32       ` Damien Le Moal
2021-01-28  9:33       ` Christoph Hellwig
2021-01-28  9:33         ` Christoph Hellwig
2021-01-28 11:43   ` Johannes Thumshirn
2021-01-28 11:43     ` Johannes Thumshirn
2021-01-28  4:47 ` [PATCH v4 8/8] sd_zbc: clear zone resources for non-zoned case Damien Le Moal
2021-01-28  4:47   ` Damien Le Moal
2021-01-28  5:38   ` Chaitanya Kulkarni
2021-01-28  5:38     ` Chaitanya Kulkarni
2021-01-28  5:40     ` Damien Le Moal
2021-01-28  5:40       ` Damien Le Moal
2021-01-28  9:24   ` Christoph Hellwig
2021-01-28  9:24     ` Christoph Hellwig
2021-01-28  9:36     ` Damien Le Moal
2021-01-28  9:36       ` Damien Le Moal
2021-01-28 11:48   ` Johannes Thumshirn
2021-01-28 11:48     ` Johannes Thumshirn
2021-02-05  2:56   ` Martin K. Petersen
2021-02-05  2:56     ` Martin K. Petersen
2021-02-04  8:47 ` [PATCH v4 0/8] block: add zone write granularity limit Damien Le Moal
2021-02-04  8:47   ` Damien Le Moal
2021-02-08 17:17   ` Christoph Hellwig
2021-02-08 17:17     ` Christoph Hellwig
2021-02-10 14:45 ` Jens Axboe [this message]
2021-02-10 14:45   ` 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=cfe15751-e07e-101f-49d8-a2f184e30618@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=chaitanya.kulkarni@wdc.com \
    --cc=damien.lemoal@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.