> +struct blk_zoned {
> + unsigned intnr_zones;
> + unsigned long *seq_zones;
> +};
> +
> struct blk_zone_report_hdr {
> unsigned intnr_zones;
> u8 padding[60];
> @@ -492,6 +497,10 @@ struct request_queue {
> struct blk_integrity integrity;
>
On Fri, 2017-09-15 at 19:06 +0900, Damien Le Moal wrote:
> @@ -492,6 +497,10 @@ struct request_queue {
> struct blk_integrity integrity;
> #endif /* CONFIG_BLK_DEV_INTEGRITY */
>
> +#ifdef CONFIG_BLK_DEV_ZONED
> + struct blk_zonedzoned;
> +#endif
> +
> #ifdef CONFIG_PM
Components relying only on the requeuest_queue structure for managing
and controlling block devices (e.g. I/O schedulers) have a limited
view/knowledged of the device being controlled. For instance, the device
capacity cannot be known easily, which for a zoned block device also
result in the
3 matches
Mail list logo