From: sagi@grimberg.me (Sagi Grimberg)
Subject: [PATCH 4/5] nvme: move namespace scanning to core
Date: Mon, 18 Apr 2016 22:41:36 +0300 [thread overview]
Message-ID: <57153870.9050306@grimberg.me> (raw)
In-Reply-To: <20160418184903.GD4640@localhost.localdomain>
>> Why does the affinity hints setting needs to happen
>> after the ns scan?
>
> The driver has no idea what queues are associated to which CPU(s) until
> after the namespaces are registered with blk-mq. We need to know that
> mapping before providing affinity hints.
So the name made me think at first that this callout is related
to ns-scanning (like the driver needs something to finish the scan), is
post_scan a better name?
next prev parent reply other threads:[~2016-04-18 19:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 12:34 proper controller state machine and more common code Christoph Hellwig
2016-04-18 12:34 ` [PATCH 1/5] nvme: remove the io_incapable method Christoph Hellwig
2016-04-18 12:34 ` [PATCH 2/5] nvme: introduce a controller state machine Christoph Hellwig
2016-04-18 18:36 ` Sagi Grimberg
2016-04-18 20:17 ` Christoph Hellwig
2016-04-18 20:30 ` Sagi Grimberg
2016-04-19 18:25 ` Christoph Hellwig
2016-04-19 18:35 ` Sagi Grimberg
2016-04-19 18:37 ` Christoph Hellwig
2016-04-20 17:25 ` Sagi Grimberg
2016-04-18 12:34 ` [PATCH 3/5] nvme: tighten up state check for namespace scanning Christoph Hellwig
2016-04-18 18:40 ` Sagi Grimberg
2016-04-18 12:34 ` [PATCH 4/5] nvme: move namespace scanning to core Christoph Hellwig
2016-04-18 18:46 ` Sagi Grimberg
2016-04-18 18:49 ` Keith Busch
2016-04-18 19:41 ` Sagi Grimberg [this message]
2016-04-18 20:17 ` Christoph Hellwig
2016-04-18 12:34 ` [PATCH 5/5] nvme: move AER handling to common code Christoph Hellwig
2016-04-20 17:26 ` Sagi Grimberg
-- strict thread matches above, loose matches on Subject: below --
2016-04-26 11:51 proper controller state machine and more common code V2 Christoph Hellwig
2016-04-26 11:51 ` [PATCH 4/5] nvme: move namespace scanning to core Christoph Hellwig
2016-04-26 17:16 ` Jon Derrick
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=57153870.9050306@grimberg.me \
--to=sagi@grimberg.me \
/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.