From: Ming Lei <ming.lei@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Yi Zhang <yi.zhang@redhat.com>,
Bob Liu <bob.liu@oracle.com>
Subject: Re: [PATCH V2] blk-mq: balance mapping between present CPUs and queues
Date: Mon, 5 Aug 2019 08:57:18 +0800 [thread overview]
Message-ID: <20190805005717.GB3449@ming.t460p> (raw)
In-Reply-To: <20190725094146.18560-1-ming.lei@redhat.com>
On Thu, Jul 25, 2019 at 05:41:46PM +0800, Ming Lei wrote:
> Spread queues among present CPUs first, then building 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 unbalanced mapping
> between present 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>
> Cc: Bob Liu <bob.liu@oracle.com>
> Signed-off-by: Ming Lei <ming.lei@redhat.com>
> ---
>
> V2:
> - make sure that sequential mapping can be done
>
> block/blk-mq-cpumap.c | 29 ++++++++++++++++++++++-------
> 1 file changed, 22 insertions(+), 7 deletions(-)
>
> diff --git a/block/blk-mq-cpumap.c b/block/blk-mq-cpumap.c
> index f945621a0e8f..0157f2b3485a 100644
> --- a/block/blk-mq-cpumap.c
> +++ b/block/blk-mq-cpumap.c
> @@ -15,10 +15,10 @@
> #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,
> + unsigned int nr_queues, const int q)
> {
> - return qmap->queue_offset + (cpu % nr_queues);
> + return qmap->queue_offset + (q % nr_queues);
> }
>
> static int get_first_sibling(unsigned int cpu)
> @@ -36,21 +36,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, nr_queues, 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);
> + if (q < nr_queues) {
> + map[cpu] = queue_index(qmap, nr_queues, q++);
> } else {
> first_sibling = get_first_sibling(cpu);
> if (first_sibling == cpu)
> - map[cpu] = cpu_to_queue_index(qmap, nr_queues, cpu);
> + map[cpu] = queue_index(qmap, nr_queues, q++);
> else
> map[cpu] = map[first_sibling];
> }
Hi Jens,
Could you consider to merge this patch to 5.4?
Thanks,
Ming
next prev parent reply other threads:[~2019-08-05 0:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 9:41 [PATCH V2] blk-mq: balance mapping between present CPUs and queues Ming Lei
2019-07-25 9:50 ` Bob Liu
2019-08-05 0:57 ` Ming Lei [this message]
2019-08-05 3:43 ` 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=20190805005717.GB3449@ming.t460p \
--to=ming.lei@redhat.com \
--cc=axboe@kernel.dk \
--cc=bob.liu@oracle.com \
--cc=linux-block@vger.kernel.org \
--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