From: Jens Axboe <axboe@kernel.dk>
To: Ming Lei <ming.lei@redhat.com>
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: Sun, 4 Aug 2019 20:43:27 -0700 [thread overview]
Message-ID: <3bf36c69-d6e0-2e5b-5d45-2e2af815a80c@kernel.dk> (raw)
In-Reply-To: <20190725094146.18560-1-ming.lei@redhat.com>
On 7/25/19 2:41 AM, 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.
LGTM, queued up for some testing.
--
Jens Axboe
prev parent reply other threads:[~2019-08-05 3:43 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
2019-08-05 3:43 ` Jens Axboe [this message]
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=3bf36c69-d6e0-2e5b-5d45-2e2af815a80c@kernel.dk \
--to=axboe@kernel.dk \
--cc=bob.liu@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).