public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Jesse Barnes <jbarnes@engr.sgi.com>
Cc: linux-kernel@vger.kernel.org, linux-ia64@vger.kernel.org,
	John Hawkes <hawkes@sgi.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] add scheduler domains for ia64
Date: Fri, 20 Aug 2004 02:11:06 +0000	[thread overview]
Message-ID: <41255DBA.3030909@yahoo.com.au> (raw)
In-Reply-To: <200408171657.32357.jbarnes@engr.sgi.com>

Jesse Barnes wrote:
> On Saturday, August 14, 2004 8:54 pm, Nick Piggin wrote:
> 
>>Yeah, all the SD_*_INIT values are overridable. We could even say, put
>>in an SD_NODE2_INIT for a 2nd level NUMA domain in the generic code,
>>for example.
> 
> 
> Yeah, we'll need different values for each level in the hierarchy.
> 
> 
>>I'd say your closest-node setup would probably get close to what you want.
>>The main thing you want is to not do huge amounts of balancing work in
>>interrupt context, and also not to move a task from one side of the
>>system to the other when one node is a little bit out of balance.
>>
>>I guess if you want to do anything fancier then we can take a look at
>>re-exporting the domain setup.
> 
> 
> Ok, sounds good.  How does this look?  It sits on top of 2.6.8.1-mm1, ripping 
> out the ia64 specific bits and moving things to sched.c.  I've also added an 
> ia64 specific SD_NODE_INIT and an #if !defined to sched.c
> 

Sorry I haven't replied earlier.  I think this looks good, provided
it does the right thing for you (I can't test it myself). Send it to
Andrew to get merged if you'd like.

  reply	other threads:[~2004-08-20  2:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-13 18:08 [PATCH] add scheduler domains for ia64 Jesse Barnes
2004-08-14  3:23 ` Nick Piggin
2004-08-14 20:52   ` Jesse Barnes
2004-08-15  0:54     ` Nick Piggin
2004-08-17 20:57       ` Jesse Barnes
2004-08-20  2:11         ` Nick Piggin [this message]
2004-08-20  2:22           ` Jesse Barnes
2004-08-20  6:28             ` Andrew Morton
2004-08-20 14:57               ` Jesse Barnes
2004-08-20  8:06             ` Ingo Molnar

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=41255DBA.3030909@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=hawkes@sgi.com \
    --cc=jbarnes@engr.sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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