From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@meta.com>, linux-block@vger.kernel.org
Cc: hch@lst.de, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH] block: enable passthrough command statistics
Date: Wed, 2 Oct 2024 19:30:06 -0600 [thread overview]
Message-ID: <11ac4a76-0a54-4d30-abd7-0b97f5c8bedd@kernel.dk> (raw)
In-Reply-To: <20241002210744.72321-1-kbusch@meta.com>
On 10/2/24 3:07 PM, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> Applications using the passthrough interfaces for advance protocol IO
> want to continue seeing the disk stats. These requests had been fenced
> off from this block layer feature. While the block layer doesn't
> necessarily know what a passthrough command does, we do know the data
> size and direction, which is enough to account for the command's stats.
>
> Since tracking these has the potential to produce unexpected results,
> the passthrough stats are locked behind a new queue feature flag that
> needs to be enabled using the /sys/block/<dev>/queue/iostats attribute.
Looks good go me in terms of allowing passthrough stats, and adding the
0/1/2 for iostats (like we do for nomerge too, for example). Minor nit
below.
> diff --git a/block/blk-sysfs.c b/block/blk-sysfs.c
> index e85941bec857b..99f438beb6c67 100644
> --- a/block/blk-sysfs.c
> +++ b/block/blk-sysfs.c
> @@ -246,7 +246,6 @@ static ssize_t queue_##_name##_store(struct gendisk *disk, \
>
> QUEUE_SYSFS_FEATURE(rotational, BLK_FEAT_ROTATIONAL)
> QUEUE_SYSFS_FEATURE(add_random, BLK_FEAT_ADD_RANDOM)
> -QUEUE_SYSFS_FEATURE(iostats, BLK_FEAT_IO_STAT)
> QUEUE_SYSFS_FEATURE(stable_writes, BLK_FEAT_STABLE_WRITES);
>
> #define QUEUE_SYSFS_FEATURE_SHOW(_name, _feature) \
> @@ -272,6 +271,40 @@ static ssize_t queue_nr_zones_show(struct gendisk *disk, char *page)
> return queue_var_show(disk_nr_zones(disk), page);
> }
>
> +static ssize_t queue_iostats_show(struct gendisk *disk, char *page)
> +{
> + return queue_var_show((bool)blk_queue_passthrough_stat(disk->queue) +
> + (bool)blk_queue_io_stat(disk->queue), page);
> +}
> +
> +static ssize_t queue_iostats_store(struct gendisk *disk, const char *page,
> + size_t count)
> +{
> + struct queue_limits lim;
> + unsigned long ios;
> + ssize_t ret;
> +
> + ret = queue_var_store(&ios, page, count);
> + if (ret < 0)
> + return ret;
> +
> + lim = queue_limits_start_update(disk->queue);
> + if (!ios)
> + lim.features &= ~(BLK_FEAT_IO_STAT | BLK_FEAT_PASSTHROUGH_STAT);
> + else if (ios == 2)
> + lim.features |= BLK_FEAT_IO_STAT | BLK_FEAT_PASSTHROUGH_STAT;
> + else if (ios == 1) {
> + lim.features |= BLK_FEAT_IO_STAT;
> + lim.features &= ~BLK_FEAT_PASSTHROUGH_STAT;
> + }
Nit: use braces for all of them, if one requires it. And might be
cleaner to simply do:
lim = queue_limits_start_update(disk->queue);
lim.features &= ~(BLK_FEAT_IO_STAT | BLK_FEAT_PASSTHROUGH_STAT);
if (ios == 2)
lim.features |= BLK_FEAT_IO_STAT | BLK_FEAT_PASSTHROUGH_STAT;
else if (ios == 1)
lim.features |= BLK_FEAT_IO_STAT;
and then I guess the braces comment no longer applies.
--
Jens Axboe
next prev parent reply other threads:[~2024-10-03 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 21:07 [PATCH] block: enable passthrough command statistics Keith Busch
2024-10-03 1:30 ` Jens Axboe [this message]
2024-10-03 13:00 ` Christoph Hellwig
2024-10-03 13:20 ` Jens Axboe
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=11ac4a76-0a54-4d30-abd7-0b97f5c8bedd@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-block@vger.kernel.org \
/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