Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nilay Shroff <nilay@linux.ibm.com>
To: Keith Busch <kbusch@meta.com>,
	linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Cc: axboe@kernel.dk, hch@lst.de, Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCHv2 1/2] block: export passthrough stats enabled
Date: Wed, 27 May 2026 11:45:06 +0530	[thread overview]
Message-ID: <39d29c16-8159-4765-b1e6-09a4354e33ea@linux.ibm.com> (raw)
In-Reply-To: <20260526153921.2402015-2-kbusch@meta.com>

On 5/26/26 9:09 PM, Keith Busch wrote:
> From: Keith Busch<kbusch@kernel.org>
> 
> A user can enable io accounting for passthrough requests, so export the
> helper that checks if the request should be tracked. This will enable
> stacking drivers to to report iostats for passthrough workloads.
> 
> Signed-off-by: Keith Busch<kbusch@kernel.org>
> ---
>   block/blk-mq.c         | 32 +-------------------------------
>   include/linux/blk-mq.h | 30 ++++++++++++++++++++++++++++++
>   2 files changed, 31 insertions(+), 31 deletions(-)

Looks good to me.
Reviewed-by: Nilay Shroff <nilay@linux.ibm.com>


  reply	other threads:[~2026-05-27  6:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26 15:39 [PATCHv2 0/2] block, nvme: enable passthrough iostats Keith Busch
2026-05-26 15:39 ` [PATCHv2 1/2] block: export passthrough stats enabled Keith Busch
2026-05-27  6:15   ` Nilay Shroff [this message]
2026-05-27  6:46   ` Nitesh Shetty
2026-05-27 13:14   ` Christoph Hellwig
2026-05-27 13:22     ` Keith Busch
2026-05-27 13:28       ` Christoph Hellwig
2026-05-26 15:39 ` [PATCHv2 2/2] nvme: add support multipath passthrough iostats Keith Busch
2026-05-27  6:15   ` Nilay Shroff
2026-05-27  6:46   ` Nitesh Shetty
2026-05-27 13:16   ` Christoph Hellwig
2026-05-27 13:27     ` Keith Busch

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=39d29c16-8159-4765-b1e6-09a4354e33ea@linux.ibm.com \
    --to=nilay@linux.ibm.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=kbusch@meta.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.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