From: Hannes Reinecke <hare@suse.de>
To: Damien Le Moal <damien.lemoal@wdc.com>,
linux-block@vger.kernel.org, Jens Axboe <axboe@kernel.dk>,
linux-scsi@vger.kernel.org,
"Martin K . Petersen" <martin.petersen@oracle.com>,
dm-devel@redhat.com, Mike Snitzer <snitzer@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
Matias Bjorling <matias.bjorling@wdc.com>
Subject: Re: [PATCH v3 09/11] block: Expose queue nr_zones in sysfs
Date: Fri, 12 Oct 2018 09:41:28 +0200 [thread overview]
Message-ID: <c13f3820-9a69-6a74-e967-b561d7778bcf@suse.de> (raw)
In-Reply-To: <20181012023012.29923-10-damien.lemoal@wdc.com>
On 10/12/18 4:30 AM, Damien Le Moal wrote:
> Expose through sysfs the nr_zones field of struct request_queue.
> Exposing this value helps in debugging disk issues as well as
> facilitating scripts based use of the disk (e.g. blktests).
>
> For zoned block devices, the nr_zones field indicates the total number
> of zones of the device calculated using the known disk capacity and
> zone size. This number of zones is always 0 for regular block devices.
>
> Since nr_zones is defined conditionally with CONFIG_BLK_DEV_ZONED,
> introduce the blk_queue_nr_zones() function to return the correct value
> for any device, regardless if CONFIG_BLK_DEV_ZONED is set.
>
> Signed-off-by: Damien Le Moal <damien.lemoal@wdc.com>
> ---
> block/blk-sysfs.c | 11 +++++++++++
> include/linux/blkdev.h | 10 ++++++++++
> 2 files changed, 21 insertions(+)
>
> diff --git a/block/blk-sysfs.c b/block/blk-sysfs.c
> index 3772671cf2bc..92be8092ca4f 100644
> --- a/block/blk-sysfs.c
> +++ b/block/blk-sysfs.c
> @@ -300,6 +300,11 @@ static ssize_t queue_zoned_show(struct request_queue *q, char *page)
> }
> }
>
> +static ssize_t queue_nr_zones_show(struct request_queue *q, char *page)
> +{
> + return queue_var_show(blk_queue_nr_zones(q), page);
> +}
> +
> static ssize_t queue_nomerges_show(struct request_queue *q, char *page)
> {
> return queue_var_show((blk_queue_nomerges(q) << 1) |
> @@ -637,6 +642,11 @@ static struct queue_sysfs_entry queue_zoned_entry = {
> .show = queue_zoned_show,
> };
>
> +static struct queue_sysfs_entry queue_nr_zones_entry = {
> + .attr = {.name = "nr_zones", .mode = 0444 },
> + .show = queue_nr_zones_show,
> +};
> +
> static struct queue_sysfs_entry queue_nomerges_entry = {
> .attr = {.name = "nomerges", .mode = 0644 },
> .show = queue_nomerges_show,
> @@ -727,6 +737,7 @@ static struct attribute *default_attrs[] = {
> &queue_write_zeroes_max_entry.attr,
> &queue_nonrot_entry.attr,
> &queue_zoned_entry.attr,
> + &queue_nr_zones_entry.attr,
> &queue_nomerges_entry.attr,
> &queue_rq_affinity_entry.attr,
> &queue_iostats_entry.attr,
> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h
> index c24969b1741b..879753b10263 100644
> --- a/include/linux/blkdev.h
> +++ b/include/linux/blkdev.h
> @@ -804,6 +804,11 @@ static inline unsigned int blk_queue_zone_sectors(struct request_queue *q)
> }
>
> #ifdef CONFIG_BLK_DEV_ZONED
> +static inline unsigned int blk_queue_nr_zones(struct request_queue *q)
> +{
> + return blk_queue_is_zoned(q) ? q->nr_zones : 0;
> +}
> +
> static inline unsigned int blk_queue_zone_no(struct request_queue *q,
> sector_t sector)
> {
> @@ -819,6 +824,11 @@ static inline bool blk_queue_zone_is_seq(struct request_queue *q,
> return false;
> return test_bit(blk_queue_zone_no(q, sector), q->seq_zones_bitmap);
> }
> +#else /* CONFIG_BLK_DEV_ZONED */
> +static inline unsigned int blk_queue_nr_zones(struct request_queue *q)
> +{
> + return 0;
> +}
> #endif /* CONFIG_BLK_DEV_ZONED */
>
> static inline bool rq_is_sync(struct request *rq)
>
Actually, we should be checking whether we can't blank out this
attribute via the is_visible mechanism; after all, not every block
device is zoned, and those which are not have no need of the attribute...
Cheers,
Hannes
--
Dr. Hannes Reinecke Teamlead Storage & Networking
hare@suse.de +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2018-10-12 7:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-12 2:30 [PATCH v3 00/11] Zoned block device support improvements Damien Le Moal
2018-10-12 2:30 ` [PATCH v3 01/11] scsi: sd_zbc: Rearrange code Damien Le Moal
2018-10-12 7:29 ` Hannes Reinecke
2018-10-12 2:30 ` [PATCH v3 02/11] scsi: sd_zbc: Reduce boot device scan and revalidate time Damien Le Moal
2018-10-12 7:33 ` Hannes Reinecke
2018-10-12 7:48 ` Damien Le Moal
2018-10-12 10:28 ` Matias Bjorling
2018-10-12 2:30 ` [PATCH v3 03/11] scsi: sd_zbc: Fix sd_zbc_check_zones() error checks Damien Le Moal
2018-10-12 7:35 ` Hannes Reinecke
2018-10-12 7:50 ` Damien Le Moal
2018-10-12 2:30 ` [PATCH v3 04/11] block: Introduce blkdev_nr_zones() helper Damien Le Moal
2018-10-12 7:36 ` Hannes Reinecke
2018-10-12 2:30 ` [PATCH v3 05/11] block: Limit allocation of zone descriptors for report zones Damien Le Moal
2018-10-12 7:36 ` Hannes Reinecke
2018-10-12 2:30 ` [PATCH v3 06/11] block: Introduce BLKGETZONESZ ioctl Damien Le Moal
2018-10-12 7:37 ` Hannes Reinecke
2018-10-12 8:23 ` Christoph Hellwig
2018-10-12 2:30 ` [PATCH v3 07/11] block: Introduce BLKGETNRZONES ioctl Damien Le Moal
2018-10-12 7:37 ` Hannes Reinecke
2018-10-12 8:23 ` Christoph Hellwig
2018-10-12 2:30 ` [PATCH v3 08/11] block: Improve zone reset execution Damien Le Moal
2018-10-12 7:39 ` Hannes Reinecke
2018-10-12 2:30 ` [PATCH v3 09/11] block: Expose queue nr_zones in sysfs Damien Le Moal
2018-10-12 7:41 ` Hannes Reinecke [this message]
2018-10-12 7:55 ` Damien Le Moal
2018-10-12 8:41 ` Hannes Reinecke
2018-10-12 8:28 ` Christoph Hellwig
2018-10-12 8:29 ` Christoph Hellwig
2018-10-12 2:30 ` [PATCH v3 10/11] block: add a report_zones method Damien Le Moal
2018-10-12 7:42 ` Hannes Reinecke
2018-10-12 2:30 ` [PATCH v3 11/11] block: Introduce blk_revalidate_disk_zones() Damien Le Moal
2018-10-12 7:44 ` Hannes Reinecke
2018-10-12 8:30 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c13f3820-9a69-6a74-e967-b561d7778bcf@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=damien.lemoal@wdc.com \
--cc=dm-devel@redhat.com \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=matias.bjorling@wdc.com \
--cc=snitzer@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox