From: "Ramia, Kannan Babu" <kannan.babu.ramia@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] eal: fix linuxapp numa node detection
Date: Thu, 23 Apr 2015 05:11:06 +0000 [thread overview]
Message-ID: <682698A055A0F44AA47192B2014114972AE656CC@BGSMSX102.gar.corp.intel.com> (raw)
In-Reply-To: <1429709515-14361-1-git-send-email-bruce.richardson@intel.com>
BTW, the BIOS fix has been posted for the NUMA node reporting issue in Linux kernel when COD is disabled. Now the /sys/devices/*/*/numa_node will provide you the correct information.
Regards
Kannan Babu
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Bruce Richardson
Sent: Wednesday, April 22, 2015 7:02 PM
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] eal: fix linuxapp numa node detection
Using the "physical_package_id" as a fallback for determining the numa node of a core tends to be unreliable. Fix this by using a detection routine which reads the numa information from /sys/devices/system/node and just returns a numa node of 0 on failure.
Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
lib/librte_eal/linuxapp/eal/eal_lcore.c | 60 ++++++++-------------------------
1 file changed, 14 insertions(+), 46 deletions(-)
diff --git a/lib/librte_eal/linuxapp/eal/eal_lcore.c b/lib/librte_eal/linuxapp/eal/eal_lcore.c
index ef8c433..f25108e 100644
--- a/lib/librte_eal/linuxapp/eal/eal_lcore.c
+++ b/lib/librte_eal/linuxapp/eal/eal_lcore.c
@@ -49,7 +49,7 @@
#define SYS_CPU_DIR "/sys/devices/system/cpu/cpu%u"
#define CORE_ID_FILE "topology/core_id"
-#define PHYS_PKG_FILE "topology/physical_package_id"
+#define NUMA_NODE_PATH "/sys/devices/system/node"
/* Check if a cpu is present by the presence of the cpu information for it */ static int @@ -66,58 +66,26 @@ cpu_detected(unsigned lcore_id)
return 1;
}
-/* Get CPU socket id (NUMA node) by reading directory
- * /sys/devices/system/cpu/cpuX looking for symlink "nodeY"
- * which gives the NUMA topology information.
- * Note: physical package id != NUMA node, but we use it as a
- * fallback for kernels which don't create a nodeY link
+/*
+ * Get CPU socket id (NUMA node) for a logical core.
+ *
+ * This searches each nodeX directories in /sys for the symlink for the
+given
+ * lcore_id and returns the numa node where the lcore is found. If
+lcore is not
+ * found on any numa node, returns zero.
*/
unsigned
eal_cpu_socket_id(unsigned lcore_id)
{
- const char node_prefix[] = "node";
- const size_t prefix_len = sizeof(node_prefix) - 1;
- char path[PATH_MAX];
- DIR *d = NULL;
- unsigned long id = 0;
- struct dirent *e;
- char *endptr = NULL;
-
- int len = snprintf(path, sizeof(path),
- SYS_CPU_DIR, lcore_id);
- if (len <= 0 || (unsigned)len >= sizeof(path))
- goto err;
+ unsigned socket;
- d = opendir(path);
- if (!d)
- goto err;
+ for (socket = 0; socket < RTE_MAX_NUMA_NODES; socket++) {
+ char path[PATH_MAX];
- while ((e = readdir(d)) != NULL) {
- if (strncmp(e->d_name, node_prefix, prefix_len) == 0) {
- id = strtoul(e->d_name+prefix_len, &endptr, 0);
- break;
- }
- }
- if (endptr == NULL || *endptr!='\0' || endptr == e->d_name+prefix_len) {
- RTE_LOG(WARNING, EAL, "Cannot read numa node link "
- "for lcore %u - using physical package id instead\n",
- lcore_id);
-
- len = snprintf(path, sizeof(path), SYS_CPU_DIR "/%s",
- lcore_id, PHYS_PKG_FILE);
- if (len <= 0 || (unsigned)len >= sizeof(path))
- goto err;
- if (eal_parse_sysfs_value(path, &id) != 0)
- goto err;
+ snprintf(path, sizeof(path),"%s/node%u/cpu%u", NUMA_NODE_PATH,
+ socket, lcore_id);
+ if (access(path, F_OK) == 0)
+ return socket;
}
- closedir(d);
- return (unsigned)id;
-
-err:
- if (d)
- closedir(d);
- RTE_LOG(ERR, EAL, "Error getting NUMA socket information from %s "
- "for lcore %u - assuming NUMA socket 0\n", SYS_CPU_DIR, lcore_id);
return 0;
}
--
2.1.0
prev parent reply other threads:[~2015-04-23 5:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 13:31 Bruce Richardson
2015-04-22 15:44 ` Stephen Hemminger
2015-06-03 16:07 ` Thomas Monjalon
2015-04-23 5:11 ` Ramia, Kannan Babu [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=682698A055A0F44AA47192B2014114972AE656CC@BGSMSX102.gar.corp.intel.com \
--to=kannan.babu.ramia@intel.com \
--cc=dev@dpdk.org \
/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).