From: Dinakar Guniguntala <dino@in.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: John Hawkes <hawkes@jackhammer.engr.sgi.com>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
pj@sgi.com, nickpiggin@yahoo.com.au, akpm@osdl.org
Subject: Re: [PATCH] ia64 cpuset + build_sched_domains() mangles structures
Date: Mon, 22 Aug 2005 14:26:14 +0000 [thread overview]
Message-ID: <20050822141414.GB7686@in.ibm.com> (raw)
In-Reply-To: <20050822070834.GA16722@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 720 bytes --]
On Mon, Aug 22, 2005 at 09:08:34AM +0200, Ingo Molnar wrote:
>
> in terms of 2.6.14, the replacement patch below also does what i always
> wanted to do: to merge the ia64-specific build_sched_domains() code back
> into kernel/sched.c. I've done this by taking your improved dynamic
> build-domains code and putting it into kernel/sched.c.
>
Ingo, one change required to your patch and the exclusive
cpuset functionality seems to work fine on a NUMA ppc64 box.
I am still running some of my dynamic sched domain tests. So far
it seems to be holding ok.
Any idea why the ia64 stuff was forked in the first place?
The patch below is on top of your patch. (This is the earlier patch
John had sent)
-Dinakar
[-- Attachment #2: sd-numa.patch --]
[-- Type: text/plain, Size: 447 bytes --]
diff -Naurp linux-2.6.13-rc6.ingo/kernel/sched.c linux-2.6.13-rc6/kernel/sched.c
--- linux-2.6.13-rc6.ingo/kernel/sched.c 2005-08-22 19:23:06.000000000 +0530
+++ linux-2.6.13-rc6/kernel/sched.c 2005-08-22 19:36:45.000000000 +0530
@@ -5192,7 +5192,7 @@ next_sg:
#endif
/* Attach the domains */
- for_each_online_cpu(i) {
+ for_each_cpu_mask(i, *cpu_map) {
struct sched_domain *sd;
#ifdef CONFIG_SCHED_SMT
sd = &per_cpu(cpu_domains, i);
next prev parent reply other threads:[~2005-08-22 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-20 14:50 [PATCH] ia64 cpuset + build_sched_domains() mangles structures John Hawkes
2005-08-22 7:08 ` Ingo Molnar
2005-08-22 14:26 ` Dinakar Guniguntala [this message]
2005-08-22 16:07 ` Ingo Molnar
2005-08-22 20:28 ` Dinakar Guniguntala
2005-08-22 20:30 ` Dinakar Guniguntala
2005-09-02 14:59 ` Dinakar Guniguntala
2005-08-22 20:38 ` Paul Jackson
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=20050822141414.GB7686@in.ibm.com \
--to=dino@in.ibm.com \
--cc=akpm@osdl.org \
--cc=hawkes@jackhammer.engr.sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@sgi.com \
/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