Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: GDQ0hGp9tiI2h++dOOJgSgoVgQqLWu/kYSG4AcnI5b005EY5W42uwA8Hqh/VGOY5T+fs+qTPti
 RBqStqPRbHy2PeLd5mQSM/Bw/7IkiO+gVNq/esHG+VzFsJtOSltyIQmJtvdHQix+rSiGggxafv
 Pbe7LtQstA0/1BTZyH15pLnO1sjZoO76Z71gsQd6qfycDj+nlmUAu/Qj1HjftyisHGFm29ESob
 WsESOmnalN+iyUK8jw7alHjTIE/SMBR6reveQLbiVXLw48BaPDjrobLIyh/GpUAfs4TqnZwJMS
 ifw=
From:   Niklas Cassel <Niklas.Cassel@wdc.com>
To:     Damien Le Moal <Damien.LeMoal@wdc.com>
CC:     Matias Bjorling <Matias.Bjorling@wdc.com>,
        "axboe@kernel.dk" <axboe@kernel.dk>,
        "kbusch@kernel.org" <kbusch@kernel.org>, "hch@lst.de" <hch@lst.de>,
        "sagi@grimberg.me" <sagi@grimberg.me>,
        "martin.petersen@oracle.com" <martin.petersen@oracle.com>,
        Hans Holmberg <Hans.Holmberg@wdc.com>,
        "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
        "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH 1/2] block: add zone_desc_ext_bytes to sysfs
Thread-Topic: [PATCH 1/2] block: add zone_desc_ext_bytes to sysfs
Thread-Index: AQHWTaAfatwqFYUzT0SXO2cOAFMc8qjvTS8A
Date:   Mon, 29 Jun 2020 09:03:58 +0000
Message-ID: <20200629090356.GA521026@localhost.localdomain>
References: <20200628230102.26990-1-matias.bjorling@wdc.com>
 <20200628230102.26990-2-matias.bjorling@wdc.com>
 <CY4PR04MB375197387D94CE4E60E836F4E76E0@CY4PR04MB3751.namprd04.prod.outlook.com>
In-Reply-To: <CY4PR04MB375197387D94CE4E60E836F4E76E0@CY4PR04MB3751.namprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
wdcipoutbound: EOP-TRUE
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <16E428DEE464C14EBD113635E6B45B7C@namprd04.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 8169bcc9-24b6-45e1-2e48-08d81c0b5c11
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jun 2020 09:03:58.6103
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: b61c8803-16f3-4c35-9b17-6f65f441df86
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: W3OzWRj0BZ2GupmMs1QpEm3RvQQi2ooNGFhVCW2hSZjCQSe8IGR/4UEnJNCFlT5kZEve/UrIoGpIFX7vXSeuoQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR04MB5783
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Jun 29, 2020 at 12:52:46AM +0000, Damien Le Moal wrote:
> On 2020/06/29 8:01, Matias Bjorling wrote:
> > The NVMe Zoned Namespace Command Set adds support for associating
> > data to a zone through the Zone Descriptor Extension feature.
> >=20
> > The Zone Descriptor Extension size is fixed to a multiple of 64
> > bytes. A value of zero communicates the feature is not available.
> > A value larger than zero communites the feature is available, and
> > the specified Zone Descriptor Extension size in bytes.
> >=20
> > The Zone Descriptor Extension feature is only available in the
> > NVMe Zoned Namespaces Command Set. Devices that supports ZAC/ZBC
> > therefore reports this value as zero, where as the NVMe device
> > driver reports the Zone Descriptor Extension size from the
> > specific device.
> >=20
> > Signed-off-by: Matias Bj=F8rling <matias.bjorling@wdc.com>
> > ---
> >  Documentation/block/queue-sysfs.rst |  6 ++++++
> >  block/blk-sysfs.c                   | 15 ++++++++++++++-
> >  drivers/nvme/host/zns.c             |  1 +
> >  drivers/scsi/sd_zbc.c               |  1 +
> >  include/linux/blkdev.h              | 22 ++++++++++++++++++++++
> >  5 files changed, 44 insertions(+), 1 deletion(-)
> >=20
> > diff --git a/Documentation/block/queue-sysfs.rst b/Documentation/block/=
queue-sysfs.rst
> > index f261a5c84170..c4fa195c87b4 100644

(snip)

> >  static struct queue_sysfs_entry queue_nomerges_entry =3D {
> >  	.attr =3D {.name =3D "nomerges", .mode =3D 0644 },
> >  	.show =3D queue_nomerges_show,
> > @@ -787,6 +798,7 @@ static struct attribute *queue_attrs[] =3D {
> >  	&queue_nr_zones_entry.attr,
> >  	&queue_max_open_zones_entry.attr,
> >  	&queue_max_active_zones_entry.attr,
>=20
> Which tree is this patch based on ? Not I have seen any patch introducing=
 max
> active zones.

The cover letter forgot to mention this patch series' dependencies.
I assume that it is based on the following patch series:
https://lore.kernel.org/linux-block/20200622162530.1287650-1-kbusch@kernel.=
org/
https://lore.kernel.org/linux-block/20200616102546.491961-1-niklas.cassel@w=
dc.com/


Kind regards,
Niklas=