From: Anton Blanchard <anton@samba.org>
To: akpm@osdl.org
Cc: paulus@samba.org, linux-kernel@vger.kernel.org
Subject: [PATCH] [ppc64] Allow SD_NODES_PER_DOMAIN to be overridden
Date: Thu, 2 Sep 2004 22:39:52 +1000 [thread overview]
Message-ID: <20040902123952.GE26072@krispykreme> (raw)
In-Reply-To: <20040902123713.GD26072@krispykreme>
Allow SD_NODES_PER_DOMAIN to be overridden.
On ppc64 set this at 16 so our top level scheduling domains will
include all nodes.
Signed-off-by: Anton Blanchard <anton@samba.org>
diff -puN include/asm-ppc64/processor.h~fix_smt include/asm-ppc64/processor.h
--- foobar2/include/asm-ppc64/processor.h~fix_smt 2004-09-02 22:22:49.861931162 +1000
+++ foobar2-anton/include/asm-ppc64/processor.h 2004-09-02 22:27:15.829370041 +1000
@@ -620,6 +620,8 @@ static inline void prefetchw(const void
#define HAVE_ARCH_PICK_MMAP_LAYOUT
+#define SD_NODES_PER_DOMAIN 16
+
#endif /* __KERNEL__ */
#endif /* ASSEMBLY */
diff -puN kernel/sched.c~fix_smt kernel/sched.c
--- foobar2/kernel/sched.c~fix_smt 2004-09-02 22:28:29.144791718 +1000
+++ foobar2-anton/kernel/sched.c 2004-09-02 22:28:32.859032577 +1000
@@ -4305,7 +4305,9 @@ __init static int cpu_to_phys_group(int
#ifdef CONFIG_NUMA
/* Number of nearby nodes in a node's scheduling domain */
+#ifndef SD_NODES_PER_DOMAIN
#define SD_NODES_PER_DOMAIN 4
+#endif
static DEFINE_PER_CPU(struct sched_domain, node_domains);
static struct sched_group sched_group_nodes[MAX_NUMNODES];
_
next prev parent reply other threads:[~2004-09-02 12:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 12:37 [PATCH] [ppc64] cleanup asm/processor.h Anton Blanchard
2004-09-02 12:39 ` Anton Blanchard [this message]
[not found] ` <20040904153316.GB7716@krispykreme>
[not found] ` <413A1052.6020400@yahoo.com.au>
[not found] ` <200409050824.47853.jbarnes@engr.sgi.com>
2004-09-06 2:54 ` [PATCH] [ppc64] Allow SD_NODES_PER_DOMAIN to be overridden Nick Piggin
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=20040902123952.GE26072@krispykreme \
--to=anton@samba.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.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