From: Anton Blanchard <anton@samba.org>
To: torvalds@osdl.org
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] fix NUMA compile with large cpumasks
Date: Sat, 13 Mar 2004 21:23:04 +1100 [thread overview]
Message-ID: <20040313102303.GC27964@krispykreme> (raw)
Hi,
The recent NUMA changes fail to compile with large cpumasks, we need
to use a temporary to get around the type checking.
Anton
---
gr26_work-anton/mm/page_alloc.c | 5 ++++-
1 files changed, 4 insertions(+), 1 deletion(-)
diff -puN mm/page_alloc.c~numacompile mm/page_alloc.c
--- gr26_work/mm/page_alloc.c~numacompile 2004-03-13 02:27:10.474086886 -0600
+++ gr26_work-anton/mm/page_alloc.c 2004-03-13 02:28:15.514771414 -0600
@@ -1155,6 +1155,8 @@ static int __init find_next_best_node(in
int best_node = -1;
for (i = 0; i < numnodes; i++) {
+ cpumask_t tmp;
+
/* Start from local node */
n = (node+i)%numnodes;
@@ -1166,7 +1168,8 @@ static int __init find_next_best_node(in
val = node_distance(node, n);
/* Give preference to headless and unused nodes */
- if (!cpus_empty(node_to_cpumask(n)))
+ tmp = node_to_cpumask(n);
+ if (!cpus_empty(tmp))
val += PENALTY_FOR_NODE_WITH_CPUS;
/* Slight preference for less loaded node */
_
reply other threads:[~2004-03-13 10:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040313102303.GC27964@krispykreme \
--to=anton@samba.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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