From: axboe@kernel.dk (Jens Axboe)
Subject: [PATCH] NVMe: Remove remnants of cpu hotplug
Date: Tue, 09 Dec 2014 13:52:37 -0700 [thread overview]
Message-ID: <54876115.5000203@kernel.dk> (raw)
In-Reply-To: <80B89753B40C5141A3E2D53FE7A2A8A9945FE6A1@NTXBOIMBX02.micron.com>
On 12/09/2014 01:50 PM, Sam Bradshaw (sbradshaw) wrote:
>
>> I'm curious with the num_possible -> num_online change. This should be
>> handled by blk-mq, so no worries there. But how did it trigger the
>> unset CPU in the run mask? Ran into the same issue here on a different
>> test case, just curious if you looked into this.
>
> After looking into it, the issue has been fixed on your for-3.19/core
> branch due to:
>
> [PATCH] blk-mq: prevent unmapped hw queue from being scheduled
>
> It's straightforward enough to test that the fix works by setting
> possible_cpus on the kernel command line to something larger than
> online cpus.
Great, that's much preferred :-)
--
Jens Axboe
prev parent reply other threads:[~2014-12-09 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 17:43 [PATCH] NVMe: Remove remnants of cpu hotplug Sam Bradshaw
2014-12-04 17:57 ` Jens Axboe
2014-12-04 21:54 ` Sam Bradshaw (sbradshaw)
2014-12-09 20:50 ` Sam Bradshaw (sbradshaw)
2014-12-09 20:52 ` 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=54876115.5000203@kernel.dk \
--to=axboe@kernel.dk \
/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