From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 2/3] nvme-multipath: Select paths based on NUMA locality
Date: Thu, 8 Nov 2018 10:32:24 +0100 [thread overview]
Message-ID: <20181108093224.GA4624@lst.de> (raw)
In-Reply-To: <20181102095641.28504-3-hare@suse.de>
On Fri, Nov 02, 2018@10:56:40AM +0100, Hannes Reinecke wrote:
> This patch creates a per-controller map to hold the NUMA locality
> information. With that we can route I/O to the controller which is
> 'nearest' to the issuing CPU and decrease the latency there.
Well, that isn't really true. The only think it does is that it
caches the result of 'node_distance(node, ns->ctrl->numa_node)'
for each [node, ctrl] tuple, and adds a sysfs file to export that.
Please update the description. This also mean on its own the
patch isn't all that useful.
> +void nvme_set_ctrl_node(struct nvme_ctrl *ctrl, int numa_node)
> +{
> + ctrl->numa_node = numa_node;
> + if (numa_node == NUMA_NO_NODE)
> + return;
I don't think adding special cases for this degenerate case is a good
idea. Or is there a really good reason for keeping the !ctrl->node_map
case around?
> + ctrl->node_map = kzalloc(num_possible_nodes() * sizeof(int),
> + GFP_KERNEL);
This should use kcalloc, and needs to check the return value.
> - distance = node_distance(node, ns->ctrl->numa_node);
> + distance = ns->ctrl->node_map ?
> + ns->ctrl->node_map[node] : INT_MAX;
If we have to keep the special case please make this a proper if/else.
> +void nvme_mpath_balance_subsys(struct nvme_subsystem *subsys)
This name seems a little odd. Why not
nvme_mpath_calculate_node_distances or something similar that
describes what it actually does?
> +{
> + struct nvme_ctrl *ctrl;
> + int node;
> +
> + mutex_lock(&subsys->lock);
> +
> + /*
> + * Reset set NUMA distance
> + * During creation the NUMA distance is only set
> + * per controller, so after connecting the other
> + * controllers the NUMA information on the existing
> + * ones is incorrect.
> + */
Please keep the comment above the function.
> + list_for_each_entry(ctrl, &subsys->ctrls, subsys_entry) {
> + for_each_node(node) {
> + if (!ctrl->node_map)
> + continue;
If we want to keep the special case the !ctrl->node_map should be moved
outside the inner loop.
next prev parent reply other threads:[~2018-11-08 9:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 9:56 [PATCHv3 0/3] nvme: NUMA locality for fabrics Hannes Reinecke
2018-11-02 9:56 ` [PATCH 1/3] nvme: NUMA locality information " Hannes Reinecke
2018-11-08 9:22 ` Christoph Hellwig
2018-11-08 9:35 ` Hannes Reinecke
2018-11-02 9:56 ` [PATCH 2/3] nvme-multipath: Select paths based on NUMA locality Hannes Reinecke
2018-11-08 9:32 ` Christoph Hellwig [this message]
2018-11-02 9:56 ` [PATCH 3/3] nvme-multipath: automatic NUMA path balancing Hannes Reinecke
2018-11-08 9:36 ` Christoph Hellwig
2018-11-16 8:12 ` [PATCHv3 0/3] nvme: NUMA locality for fabrics Christoph Hellwig
2018-11-16 8:21 ` Hannes Reinecke
2018-11-16 8:23 ` Christoph Hellwig
2018-11-19 22:31 ` Sagi Grimberg
2018-11-20 6:12 ` Hannes Reinecke
2018-11-20 9:41 ` Christoph Hellwig
2018-11-20 15:47 ` Keith Busch
2018-11-20 19:27 ` James Smart
2018-11-21 8:36 ` Christoph Hellwig
2018-11-20 16:21 ` Hannes Reinecke
2018-11-20 18:12 ` James Smart
-- strict thread matches above, loose matches on Subject: below --
2018-10-26 12:57 [PATCHv2 " Hannes Reinecke
2018-10-26 12:57 ` [PATCH 2/3] nvme-multipath: Select paths based on NUMA locality Hannes Reinecke
2018-10-30 18:39 ` Sagi Grimberg
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=20181108093224.GA4624@lst.de \
--to=hch@lst.de \
/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).