From: Petr Holasek <pholasek@redhat.com>
To: Cliff Wickman <cpw@sgi.com>
Cc: linux-numa@vger.kernel.org, Andi Kleen <andi@firstfloor.org>,
Anton Arapov <anton@redhat.com>,
Petr Holasek <pholasek@redhat.com>
Subject: [PATCH v2 7/7] libnuma: no warnings when there are holes in numbering of nodes
Date: Thu, 23 Aug 2012 18:01:59 +0200 [thread overview]
Message-ID: <1345737719-11433-8-git-send-email-pholasek@redhat.com> (raw)
In-Reply-To: <1345737719-11433-1-git-send-email-pholasek@redhat.com>
Some machines don't even export their 0th node to acpi tables when there
is no memory installed. This patch removes warning in such cases.
Signed-off-by: Petr Holasek <pholasek@redhat.com>
---
distance.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/distance.c b/distance.c
index 2b48f97..4a26972 100755
--- a/distance.c
+++ b/distance.c
@@ -64,7 +64,7 @@ static int read_distance_table(void)
sprintf(fn, "/sys/devices/system/node/node%d/distance", nd);
dfh = fopen(fn, "r");
if (!dfh) {
- if (errno == ENOENT && nd > 0)
+ if (errno == ENOENT)
err = 0;
if (!err && nd<maxnode)
continue;
--
1.7.11.4
prev parent reply other threads:[~2012-08-23 16:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 16:01 [PATCH v2 0/7] couple of numactl-2.0.8-rc4 bugfixes and new interface Petr Holasek
2012-08-23 16:01 ` [PATCH v2 1/7] libnuma: Fix calculation of maxconfiguredcpu Petr Holasek
2012-08-23 16:01 ` [PATCH v2 2/7] libnuma: do not recalculate maxconfiguredcpu Petr Holasek
2012-08-23 16:01 ` [PATCH v2 3/7] libnuma: numa_num_possible_cpus symbol is exported from the library Petr Holasek
2012-08-23 16:01 ` [RFC PATCH v2 4/7] libnuma: introduced _all versions of numa_parse_{cpu,node}string() Petr Holasek
2012-08-23 16:01 ` [PATCH v2 5/7] libnuma: numa_parse_cpustring and similar should take a const char* parameter Petr Holasek
2012-08-23 16:01 ` [PATCH v2 6/7] libnuma: removed unused bufferlen variable Petr Holasek
2012-08-23 16:01 ` Petr Holasek [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=1345737719-11433-8-git-send-email-pholasek@redhat.com \
--to=pholasek@redhat.com \
--cc=andi@firstfloor.org \
--cc=anton@redhat.com \
--cc=cpw@sgi.com \
--cc=linux-numa@vger.kernel.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).