From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: Dimitri Sivanich <sivanich@sgi.com>,
"Siddha, Suresh B" <suresh.b.siddha@intel.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>,
John Hawkes <hawkes@sgi.com>
Subject: Re: [PATCH] consolidate sched domains
Date: Tue, 27 Jul 2004 13:28:25 +1000 [thread overview]
Message-ID: <4105CBD9.7080209@yahoo.com.au> (raw)
In-Reply-To: <200407261106.33173.jbarnes@engr.sgi.com>
Jesse Barnes wrote:
>On Sunday, July 25, 2004 9:05 pm, Nick Piggin wrote:
>
>>Yes of course, thank you.
>>
>>The fix is for cpu_to_phys_group() to just return cpu when
>>!CONFIG_SCHED_SMT.
>>
>
>Here's the node domain span stuff on top of your consolidation patch, along
>with the two fixes mentioned in this thread. It compiles and works fine on
>my small box, but I haven't tested it on a large box yet.
>
>
You'll also want Jack Steiner's one liner. (I've sent all these to Andrew.)
Looks pretty neat. It may even be usable in the generic setup code if more
architectures start needing it.
For now, put it in your arch code when it is ready to be merged up of
course.
I would be very interested to see what sort of performance improvements you
get out of the scheduler...
next prev parent reply other threads:[~2004-07-27 3:28 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
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 [this message]
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=4105CBD9.7080209@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=anton@samba.org \
--cc=hawkes@sgi.com \
--cc=jbarnes@engr.sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox