From: Ming Lei <ming.lei@redhat.com>
To: "Ewan D. Milne" <emilne@redhat.com>
Cc: linux-nvme@lists.infradead.org, tsong@purestorage.com,
jmeneghi@redhat.com, mlombard@redhat.com
Subject: Re: [PATCH 1/3] block: introduce blk_queue_nr_active()
Date: Wed, 27 Sep 2023 17:49:24 +0800 [thread overview]
Message-ID: <ZRP6pCFd8+mWpUcS@fedora> (raw)
In-Reply-To: <20230925163123.16042-2-emilne@redhat.com>
On Mon, Sep 25, 2023 at 12:31:21PM -0400, Ewan D. Milne wrote:
> Returns a count of the total number of active requests
> in a queue. For non-shared tags (the usual case) this is
> the sum of nr_active from all of the hctxs.
hctx->nr_active is only updated if BLK_MQ_F_TAG_QUEUE_SHARED is true
and blk_mq_is_shared_tags() is false, so hctx->nr_active isn't
available if BLK_MQ_F_TAG_QUEUE_SHARED is false(the usual case?).
Thanks,
Ming
next prev parent reply other threads:[~2023-09-27 9:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 16:31 [PATCH 0/3] NVMe multipath path selector enhancements Ewan D. Milne
2023-09-25 16:31 ` [PATCH 1/3] block: introduce blk_queue_nr_active() Ewan D. Milne
2023-09-25 20:56 ` Bart Van Assche
2023-09-27 14:49 ` Ewan Milne
2023-09-27 14:58 ` Bart Van Assche
2023-09-27 7:36 ` Hannes Reinecke
2023-09-27 11:37 ` Ming Lei
2023-09-27 13:34 ` Ewan Milne
2023-10-03 20:11 ` Uday Shankar
2023-10-04 9:19 ` Sagi Grimberg
2023-09-27 9:49 ` Ming Lei [this message]
2023-09-27 13:54 ` Ewan Milne
2023-09-27 10:56 ` Sagi Grimberg
2023-09-27 13:50 ` Ewan Milne
2023-09-28 10:56 ` Sagi Grimberg
2023-09-25 16:31 ` [PATCH 2/3] nvme-multipath: Implement new iopolicy "queue-depth" Ewan D. Milne
2023-09-27 7:38 ` Hannes Reinecke
2023-09-27 11:02 ` Sagi Grimberg
2023-09-27 13:42 ` Ewan Milne
2023-09-25 16:31 ` [PATCH 3/3] nvme-multipath: add "use_nonoptimized" module option Ewan D. Milne
2023-09-27 7:41 ` Hannes Reinecke
2023-09-27 11:31 ` Sagi Grimberg
2023-09-27 13:11 ` John Meneghini
2023-09-27 13:45 ` Ewan Milne
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=ZRP6pCFd8+mWpUcS@fedora \
--to=ming.lei@redhat.com \
--cc=emilne@redhat.com \
--cc=jmeneghi@redhat.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mlombard@redhat.com \
--cc=tsong@purestorage.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