From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: To: Damien Le Moal Cc: linux-scsi@vger.kernel.org, "Martin K . Petersen" , linux-block@vger.kernel.org, Jens Axboe , Christoph Hellwig , Bart Van Assche Subject: Re: [PATCH V7 1/8] block: introduce zoned block devices zone write locking From: "Martin K. Petersen" References: <20171108081118.7632-1-damien.lemoal@wdc.com> <20171108081118.7632-2-damien.lemoal@wdc.com> Date: Wed, 08 Nov 2017 18:33:19 -0500 In-Reply-To: <20171108081118.7632-2-damien.lemoal@wdc.com> (Damien Le Moal's message of "Wed, 8 Nov 2017 17:11:11 +0900") Message-ID: MIME-Version: 1.0 Content-Type: text/plain List-ID: Damien, > + * Zoned block device information for request dispatch control. > + * nr_zones is the total number of zones of the device. This is always > + * 0 for regular block devices. seq_zones_bitmap is a bitmap of nr_zones > + * bits which indicates if a zone is conventional (bit clear) or > + * sequential (bit set). seq_zones_wlock is a bitmap of nr_zones > + * bits which indicates if a zone is write locked, thatt is, if a write ^^^^^ > + * request targeting the zone was dispatched. All three fields are > + * initialized by the low level device driver. Stacking drivers > + * (device mappers) may or may not initialize these fields. > + */ > + unsigned int nr_zones; > + unsigned long *seq_zones_bitmap; > + unsigned long *seq_zones_wlock; > + > + /* Otherwise OK. Reviewed-by: Martin K. Petersen -- Martin K. Petersen Oracle Linux Engineering