From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH v4 00/11] Zoned block device support improvements To: Damien Le Moal , linux-block@vger.kernel.org, linux-scsi@vger.kernel.org, "Martin K . Petersen" , dm-devel@redhat.com, Mike Snitzer Cc: Christoph Hellwig , Matias Bjorling References: <20181012100850.23316-1-damien.lemoal@wdc.com> From: Jens Axboe Message-ID: Date: Sat, 13 Oct 2018 16:43:30 -0600 MIME-Version: 1.0 In-Reply-To: <20181012100850.23316-1-damien.lemoal@wdc.com> Content-Type: text/plain; charset=utf-8 List-ID: On 10/12/18 4:08 AM, Damien Le Moal wrote: > This series improves zoned block device support (reduce overhead) and > introduces many simplifications to the code (overall, there are more deletions > than insertions). > > In more details: > * Patches 1 to 3 are SCSI side (sd driver) cleanups and improvements reducing > the overhead of report zones command execution during disk scan and > revalidation. > * Patches 4 to 9 improve the useability and user API of zoned block devices. > * Patch 10 is the main part of this series. This patch replaces the > REQ_OP_ZONE_REPORT BIO/request operation for executing report zones commands > with a block device file operation, removing the need for the command reply > payload in-place rewriting in the BIO buffer. This leads to major > simplification of the code in many places. > * Patch 11 further simplifies the code of low level drivers by providing a > generic implementation of zoned block device request queue zone bitmaps > initialization and revalidation. > > Please consider the addition of these patches in 4.20. > Comments are as always welcome. How do we want to funnel this series? 1-3 look separate, so perhaps they should go through the scsi tree. Then I can take the rest. Or do some of the later ones depend on 1-3 being in, in terms of applying cleanly? I can also take all of them, looks like only #3 needs a SCSI ack. -- Jens Axboe