Message ID | 20200714211824.759224-1-niklas.cassel@wdc.com (mailing list archive) |
---|---|
Headers | show |
Series | Export max open zones and max active zones to sysfs | expand |
Niklas, > Export max open zones and max active zones to sysfs. Looks fine. Reviewed-by: Martin K. Petersen <martin.petersen@oracle.com>
On 7/14/20 3:18 PM, Niklas Cassel wrote: > Export max open zones and max active zones to sysfs. > > This patch series in based on Jens's linux-block/for-next branch. > > All zoned block devices in the kernel utilize the "zoned block device > support" (CONFIG_BLK_DEV_ZONED). > > The Zoned Namespace Command Set Specification defines two different > resource limits: Max Open Resources and Max Active Resources. > > The ZAC and ZBC standards define a MAXIMUM NUMBER OF OPEN SEQUENTIAL WRITE > REQUIRED ZONES field. > > > Since the ZNS Max Open Resources field has the same purpose as the ZAC/ZBC > field, (the ZNS field is 0's based, the ZAC/ZBC field isn't), create a > common "max_open_zones" definition in the sysfs documentation, and export > both the ZNS field and the ZAC/ZBC field according to this new common > definition. > > The ZNS Max Active Resources field does not have an equivalent field in > ZAC/ZBC, however, since both ZAC/ZBC and ZNS utilize the "zoned block > device support" in the kernel, create a "max_active_zones" definition in > the sysfs documentation, similar to "max_open_zones", and export it > according to this new definition. For ZAC/ZBC devices, this field will be > exported as 0, meaning "no limit". Applied, thanks.