From: Christoph Hellwig <hch@lst.de>
To: Nilay Shroff <nilay@linux.ibm.com>
Cc: John Garry <john.g.garry@oracle.com>,
linux-nvme@lists.infradead.org, hare@suse.de, kbusch@kernel.org,
hch@lst.de, sagi@grimberg.me, dwagner@suse.de,
kanie@linux.alibaba.com, jmeneghi@redhat.com,
randyj@purestorage.com, martin.petersen@oracle.com,
gjoyce@linux.ibm.com
Subject: Re: [PATCHv6 1/8] block: expose blk_stat_{enable,disable}_accounting() to drivers
Date: Fri, 22 May 2026 14:10:54 +0200 [thread overview]
Message-ID: <20260522121054.GA21338@lst.de> (raw)
In-Reply-To: <c0d1d025-0c34-4df0-a123-1324e2a99389@linux.ibm.com>
blk_stat_enable_accounting is currently only useful for blk-mq based
drivers, so please keep it there.
next prev parent reply other threads:[~2026-05-22 12:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 18:20 [PATCHv6 0/8] nvme-multipath: introduce latency I/O policy Nilay Shroff
2026-05-20 18:20 ` [PATCHv6 1/8] block: expose blk_stat_{enable,disable}_accounting() to drivers Nilay Shroff
2026-05-21 12:06 ` John Garry
2026-05-22 6:18 ` Nilay Shroff
2026-05-22 12:10 ` Christoph Hellwig [this message]
2026-05-20 18:20 ` [PATCHv6 2/8] nvme-multipath: pass I/O type to nvme_find_path() Nilay Shroff
2026-05-27 7:16 ` Hannes Reinecke
2026-05-20 18:20 ` [PATCHv6 3/8] nvme-multipath: add support for latency I/O policy Nilay Shroff
2026-05-20 18:21 ` [PATCHv6 4/8] nvme: add generic debugfs support Nilay Shroff
2026-05-20 18:21 ` [PATCHv6 5/8] nvme-multipath: add debugfs attribute latency_ewma_shift Nilay Shroff
2026-05-20 18:21 ` [PATCHv6 6/8] nvme-multipath: add debugfs attribute latency_batch_timeout Nilay Shroff
2026-05-20 18:21 ` [PATCHv6 7/8] nvme-multipath: add debugfs attribute latency_stat Nilay Shroff
2026-05-20 18:21 ` [PATCHv6 8/8] nvme-multipath: add documentation for latency I/O policy Nilay Shroff
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=20260522121054.GA21338@lst.de \
--to=hch@lst.de \
--cc=dwagner@suse.de \
--cc=gjoyce@linux.ibm.com \
--cc=hare@suse.de \
--cc=jmeneghi@redhat.com \
--cc=john.g.garry@oracle.com \
--cc=kanie@linux.alibaba.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=martin.petersen@oracle.com \
--cc=nilay@linux.ibm.com \
--cc=randyj@purestorage.com \
--cc=sagi@grimberg.me \
/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