From: Daniel Yeisley <dan.yeisley@unisys.com>
To: linux-kernel@vger.kernel.org
Cc: ak@suse.de
Subject: [PATCH] CPUs on memoryless nodes not being reassigned
Date: Wed, 26 Mar 2008 08:44:28 -0400 [thread overview]
Message-ID: <1206535469.7468.9.camel@localhost.localdomain> (raw)
When I boot with memoryless nodes on the latest 2.6.25-rc kernels, the
CPUs aren't being reassigned to nodes with memory.
Signed-off-by: Dan Yeisley <dan.yeisley@unisys.com>
---
diff -Nuar linux-2.6.25-rc6/arch/x86/kernel/setup_64.c linux-2.6.25-rc6-new/arch/x86/kernel/setup_64.c
--- linux-2.6.25-rc6/arch/x86/kernel/setup_64.c 2008-03-16 19:32:14.000000000 -0400
+++ linux-2.6.25-rc6-new/arch/x86/kernel/setup_64.c 2008-03-25 09:52:15.000000000 -0400
@@ -801,7 +801,7 @@
/* Don't do the funky fallback heuristics the AMD version employs
for now. */
node = apicid_to_node[apicid];
- if (node == NUMA_NO_NODE)
+ if (node == NUMA_NO_NODE || !node_online(node))
node = first_node(node_online_map);
numa_set_node(cpu, node);
next reply other threads:[~2008-03-26 13:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-26 12:44 Daniel Yeisley [this message]
2008-03-26 13:10 ` [PATCH] CPUs on memoryless nodes not being reassigned Ingo Molnar
2008-03-26 17:57 ` Yeisley, Dan P.
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=1206535469.7468.9.camel@localhost.localdomain \
--to=dan.yeisley@unisys.com \
--cc=ak@suse.de \
--cc=linux-kernel@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 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.