From: Bob Liu <bob.liu@oracle.com>
To: Ming Lei <ming.lei@redhat.com>, Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Yi Zhang <yi.zhang@redhat.com>
Subject: Re:[PATCH] blk-mq: balance mapping between CPUs and queues
Date: Thu, 25 Jul 2019 16:35:30 +0800 [thread overview]
Message-ID: <0225f4eb-364c-fa0c-5d72-e2a58bf9ae68@oracle.com> (raw)
In-Reply-To: <20190725075604.1106-1-ming.lei@redhat.com>
On 7/25/19 4:26 PM, Ming Lei wrote:
> Spread queues among present CPUs first, then building the mapping
> on other non-present CPUs.
>
> So we can minimize count of dead queues which are mapped by un-present
> CPUs only. Then bad IO performance can be avoided by this unbalanced
> mapping between CPUs and queues.
>
> The similar policy has been applied on Managed IRQ affinity.
>
> Reported-by: Yi Zhang <yi.zhang@redhat.com>
> Cc: Yi Zhang <yi.zhang@redhat.com>
> Signed-off-by: Ming Lei <ming.lei@redhat.com>
> ---
> block/blk-mq-cpumap.c | 34 +++++++++++++++++++++++-----------
> 1 file changed, 23 insertions(+), 11 deletions(-)
>
> diff --git a/block/blk-mq-cpumap.c b/block/blk-mq-cpumap.c
> index f945621a0e8f..e217f3404dc7 100644
> --- a/block/blk-mq-cpumap.c
> +++ b/block/blk-mq-cpumap.c
> @@ -15,10 +15,9 @@
> #include "blk.h"
> #include "blk-mq.h"
>
> -static int cpu_to_queue_index(struct blk_mq_queue_map *qmap,
> - unsigned int nr_queues, const int cpu)
> +static int queue_index(struct blk_mq_queue_map *qmap, const int q)
> {
> - return qmap->queue_offset + (cpu % nr_queues);
> + return qmap->queue_offset + q;
> }
>
> static int get_first_sibling(unsigned int cpu)
> @@ -36,23 +35,36 @@ int blk_mq_map_queues(struct blk_mq_queue_map *qmap)
> {
> unsigned int *map = qmap->mq_map;
> unsigned int nr_queues = qmap->nr_queues;
> - unsigned int cpu, first_sibling;
> + unsigned int cpu, first_sibling, q = 0;
> +
> + for_each_possible_cpu(cpu)
> + map[cpu] = -1;
> +
> + /*
> + * Spread queues among present CPUs first for minimizing
> + * count of dead queues which are mapped by all un-present CPUs
> + */
> + for_each_present_cpu(cpu) {
> + if (q >= nr_queues)
> + break;
> + map[cpu] = queue_index(qmap, q++);
> + }
>
> for_each_possible_cpu(cpu) {
> + if (map[cpu] != -1)
> + continue;
> /*
> * First do sequential mapping between CPUs and queues.
> * In case we still have CPUs to map, and we have some number of
> * threads per cores then map sibling threads to the same queue
> * for performance optimizations.
> */
> - if (cpu < nr_queues) {
> - map[cpu] = cpu_to_queue_index(qmap, nr_queues, cpu);
Why not keep this similarly?
> + first_sibling = get_first_sibling(cpu);
> + if (first_sibling == cpu) {
> + map[cpu] = queue_index(qmap, q);
> + q = (q + 1) % nr_queues;
> } else {
> - first_sibling = get_first_sibling(cpu);
> - if (first_sibling == cpu)
> - map[cpu] = cpu_to_queue_index(qmap, nr_queues, cpu);
> - else
> - map[cpu] = map[first_sibling];
> + map[cpu] = map[first_sibling];
Then no need to share queue if nr_queues is enough for all possible cpu.
Regards, -Bob
next prev parent reply other threads:[~2019-07-25 8:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 7:56 [PATCH] blk-mq: balance mapping between CPUs and queues Ming Lei
2019-07-25 8:35 ` Bob Liu [this message]
2019-07-25 9:18 ` Ming Lei
2019-07-25 9:20 ` Ming Lei
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=0225f4eb-364c-fa0c-5d72-e2a58bf9ae68@oracle.com \
--to=bob.liu@oracle.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=yi.zhang@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