From: keith.busch@linux.intel.com (Keith Busch)
Subject: [PATCH] nvme: take node locality into account when selecting a path
Date: Fri, 28 Sep 2018 08:12:57 -0600 [thread overview]
Message-ID: <20180928141256.GA21979@localhost.localdomain> (raw)
In-Reply-To: <20180927230557.29444-1-hch@lst.de>
On Thu, Sep 27, 2018@04:05:57PM -0700, Christoph Hellwig wrote:
> Make current_path an array with an entry for every possible node, and
> cache the best path on a per-node basis. Take the node distance into
> account when selecting it. This is primarily useful for dual-ported PCIe
> devices which are connected to PCIe root ports on different sockets.
>
> Signed-off-by: Christoph Hellwig <hch at lst.de>
Looks great!
Reviewed-by: Keith Busch <keith.busch at intel.com>
next prev parent reply other threads:[~2018-09-28 14:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 23:05 [PATCH] nvme: take node locality into account when selecting a path Christoph Hellwig
2018-09-28 14:12 ` Keith Busch [this message]
2018-09-28 22:31 ` Sagi Grimberg
2018-09-30 23:01 ` Christoph Hellwig
2018-10-01 19:45 ` Sagi Grimberg
2018-10-02 17:30 ` Hannes Reinecke
2018-10-02 17:39 ` Christoph Hellwig
2018-10-03 8:56 ` Hannes Reinecke
2018-10-03 12:43 ` Christoph Hellwig
2018-10-04 1:30 ` Sagi Grimberg
2018-10-04 15:40 ` Hannes Reinecke
2018-09-29 12:09 ` Hannes Reinecke
2018-09-30 22:59 ` Christoph Hellwig
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=20180928141256.GA21979@localhost.localdomain \
--to=keith.busch@linux.intel.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).