From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: Dimitri Sivanich <sivanich@sgi.com>,
Andrew Morton <akpm@osdl.org>, Anton Blanchard <anton@samba.org>,
Andi Kleen <ak@suse.de>, Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] consolidate sched domains
Date: Sat, 24 Jul 2004 13:09:20 +1000 [thread overview]
Message-ID: <4101D2E0.2000108@yahoo.com.au> (raw)
In-Reply-To: <200407231450.47070.suresh.b.siddha@intel.com>
Siddha, Suresh B wrote:
> On Friday 23 July 2004 08:30, Dimitri Sivanich wrote:
>
>>On Fri, Jul 23, 2004 at 01:18:30PM +1000, Nick Piggin wrote:
>>
>>>The attached patch is against 2.6.8-rc1-mm1. Tested on SMP, UP and SMP+HT
>>>here and it seems to be OK.
>>>
>>>I have included the cpu_sibling_map for ppc64, although Anton said he did
>>>have an implementation floating around which he would probably prefer,
>>>but I'll let him deal with that.
>>
>>Do other architectures need to define their own cpu_sibling_maps, or am I
>>missing something that would define that for IA64 and others?
>
>
> Nick means, all the architectures which use CONFIG_SCHED_SMT needs to define
> cpu_sibling_map.
>
That's right.
> Nick, aren't you missing the attached fix in your patch?
>
Indeed I am. Good catch, thanks.
> thanks,
> suresh
>
>
> ------------------------------------------------------------------------
>
> --- linux-2.6.8-rc1/kernel/sched.c~ 2004-07-23 13:19:48.000000000 -0700
> +++ linux-2.6.8-rc1/kernel/sched.c 2004-07-23 13:34:49.000000000 -0700
> @@ -3845,6 +3845,8 @@
> sd->groups->cpu_power = power;
>
> #ifdef CONFIG_NUMA
> + if (i != first_cpu(sd->groups->cpumask))
> + continue;
> sd = &per_cpu(node_domains, i);
> sd->groups->cpu_power += power;
> #endif
next prev parent reply other threads:[~2004-07-24 3:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 3:18 [PATCH] consolidate sched domains Nick Piggin
2004-07-23 5:31 ` Ingo Molnar
2004-07-23 15:30 ` Dimitri Sivanich
2004-07-23 21:50 ` Siddha, Suresh B
2004-07-24 3:09 ` Nick Piggin [this message]
2004-07-26 2:22 ` Dimitri Sivanich
2004-07-26 4:05 ` Nick Piggin
2004-07-26 18:06 ` Jesse Barnes
2004-07-27 3:28 ` Nick Piggin
2004-07-27 16:15 ` Jesse Barnes
2004-07-28 1:08 ` 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=4101D2E0.2000108@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sivanich@sgi.com \
--cc=suresh.b.siddha@intel.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 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.