linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <Damien.LeMoal@wdc.com>
To: Jens Axboe <axboe@kernel.dk>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"Martin K . Petersen" <martin.petersen@oracle.com>,
	"dm-devel@redhat.com" <dm-devel@redhat.com>,
	Mike Snitzer <snitzer@redhat.com>,
	"linux-f2fs-devel@lists.sourceforge.net"
	<linux-f2fs-devel@lists.sourceforge.net>,
	Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <yuchao0@huawei.com>
Subject: Re: [f2fs-dev] [PATCH v2 0/9] Zoned block device enhancements and zone report rework
Date: Wed, 13 Nov 2019 02:40:39 +0000	[thread overview]
Message-ID: <BYAPR04MB58165811E5614D9B0B122CB5E7760@BYAPR04MB5816.namprd04.prod.outlook.com> (raw)
In-Reply-To: a0c1c1bf-d6e5-8be1-ed99-6bfed3483d1d@kernel.dk

On 2019/11/13 11:16, Jens Axboe wrote:
> On 11/10/19 6:39 PM, Damien Le Moal wrote:
>> This series of patches introduces changes to zoned block device handling
>> code with the intent to simplify the code while optimizing run-time
>> operation, particularly in the area of zone reporting.
>>
>> The first patch lifts the device zone check code out of the sd driver
>> and reimplements these zone checks generically as part of
>> blk_revalidate_disk_zones(). This avoids zoned block device drivers to
>> have to implement these checks. The second patch simplifies this
>> function code for the !zoned case.
>>
>> The third patch is a small cleanup of zone report processing in
>> preparation for the fourth patch which removes support for partitions
>> on zoned block devices. As mentioned in that patch commit message, none
>> of the known partitioning tools support zoned devices and there are no
>> known use case in the field of SMR disks being used with partitions.
>> Dropping partition supports allows to significantly simplify the code
>> for zone report as zone sector values remapping becomes unnecessary.
>>
>> Patch 5 to 6 are small cleanups and fixes of the null_blk driver zoned
>> mode.
>>
>> The prep patch 7 optimizes zone report buffer allocation for the SCSI
>> sd driver. Finally, patch 8 introduces a new interface for report zones
>> handling using a callback function executed per zone reported by the
>> device. This allows avoiding the need to allocate large arrays of
>> blk_zone structures for the execution of zone reports. This can
>> significantly reduce memory usage and pressure on the memory management
>> system while significantly simplify the code all over.
>>
>> Overall, this series not only reduces significantly the code size, it
>> also improves run-time memory usage for zone report execution.
>>
>> This series applies cleanly on the for-next block tree on top of the
>> zone management operation series. It may however create a conflict with
>> Christoph's reqork of disk size revalidation. Please consider this
>> series for inclusion in the 5.5 kernel.
> 
> We're taking branching to new levels... I created for-5.5/zoned for this,
> which is for-5.5/block + for-5.5/drivers + for-5.5/drivers-post combined.
> The latter is a branch with the SCSI dependencies from Martin pulled in.
> 

Jens,

Thanks !

-- 
Damien Le Moal
Western Digital Research


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2019-11-13  2:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-11  2:39 [f2fs-dev] [PATCH v2 0/9] Zoned block device enhancements and zone report rework Damien Le Moal
2019-11-11  2:39 ` [f2fs-dev] [PATCH v2 1/9] block: Enhance blk_revalidate_disk_zones() Damien Le Moal
2019-11-11  2:39 ` [f2fs-dev] [PATCH v2 2/9] block: cleanup the !zoned case in blk_revalidate_disk_zones Damien Le Moal
2019-11-11  2:39 ` [f2fs-dev] [PATCH v2 3/9] block: Simplify report zones execution Damien Le Moal
2019-11-11  2:39 ` [f2fs-dev] [PATCH v2 4/9] block: Remove partition support for zoned block devices Damien Le Moal
2019-11-11  6:55   ` Hannes Reinecke
2019-11-11  2:39 ` [f2fs-dev] [PATCH v2 5/9] null_blk: clean up the block device operations Damien Le Moal
2019-11-11  2:39 ` [f2fs-dev] [PATCH v2 6/9] null_blk: clean up report zones Damien Le Moal
2019-11-11  2:39 ` [f2fs-dev] [PATCH v2 7/9] null_blk: Add zone_nr_conv to features Damien Le Moal
2019-11-11  2:39 ` [f2fs-dev] [PATCH v2 8/9] scsi: sd_zbc: Cleanup sd_zbc_alloc_report_buffer() Damien Le Moal
2019-11-11  6:56   ` Hannes Reinecke
2019-11-11 10:22   ` Christoph Hellwig
2019-11-13  1:46   ` Martin K. Petersen
2019-11-11  2:39 ` [f2fs-dev] [PATCH v2 9/9] block: rework zone reporting Damien Le Moal
2019-11-13  2:16 ` [f2fs-dev] [PATCH v2 0/9] Zoned block device enhancements and zone report rework Jens Axboe
2019-11-13  2:40   ` Damien Le Moal [this message]
2019-11-13  7:06   ` Christoph Hellwig

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=BYAPR04MB58165811E5614D9B0B122CB5E7760@BYAPR04MB5816.namprd04.prod.outlook.com \
    --to=damien.lemoal@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=snitzer@redhat.com \
    --cc=yuchao0@huawei.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).