From: axboe@fb.com (Jens Axboe)
Subject: [PATCH] NVMe: Set affinity after allocating request queues
Date: Wed, 23 Sep 2015 14:40:21 -0600 [thread overview]
Message-ID: <56030E35.3060400@fb.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1509232035500.23840@localhost.lm.intel.com>
On 09/23/2015 02:37 PM, Keith Busch wrote:
> On Thu, 3 Sep 2015, Keith Busch wrote:
>> The asynchronous namespace scanning caused affinity hints to be set
>> before
>> its tagset initialized, so there was no cpu mask to set the hint. This
>> patch moves the affinity hint setting to after namespaces are scanned.
>
> Hi Jens,
>
> Would it be okay to get this merged in for 4.3? The affinity hint is
> very important to top out performance, so this should be considered a
> bug that the setting wasn't correct.
I haven't seen this patch, but yes if it's not setting the right hints,
then it should be fixed as that is certainly a potentially big
performance issue. In general we're still in dire need of having a
proper way of having this done without a lot of driver interaction. I'd
really love to see a framework that just has the driver ask blk-mq for a
set of handlers, and blk-mq will set with the hints that it has already
assigned. I might even have promised to write this, I should get around
to do that... But I don't think it should be a gating factor for this
fix, though it still needs to get done.
--
Jens Axboe
prev parent reply other threads:[~2015-09-23 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 14:18 [PATCH] NVMe: Set affinity after allocating request queues Keith Busch
2015-09-04 8:08 ` 김경산
2015-09-04 15:12 ` Keith Busch
2015-09-23 20:37 ` Keith Busch
2015-09-23 20:40 ` 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=56030E35.3060400@fb.com \
--to=axboe@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.