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: Sat, 14 Aug 2004 03:23:47 +0000 [thread overview]
Message-ID: <411D85C3.4030808@yahoo.com.au> (raw)
In-Reply-To: <200408131108.40502.jbarnes@engr.sgi.com>
Jesse Barnes wrote:
> Nick, how does this look? It adds scheduler domain code for ia64 and replaces
> the patch in Andrew's tree. It also adds SD_NODE_INIT macros to each arch
> that has ARCH_HAS_SCHED_DOMAIN so that the balance values are more easily
> tweaked. Since the cpu span of the nodes on ia64 is smaller than the whole
> system, I also removed a WARN_ON in active_load_balance, but I'm not sure if
> that's correct.
Hi Jesse,
Andrew's latest tree should have a number of improvements and changes
to the sched domains code which you will need to synch up to.
One issue you may have is that Ingo removed the ability to have arch
code override the domain structure due to it being too hazardous for
architectures to use in this form (which I don't entirely disagree with).
Now I guess your patch could go into the generic code because it is
pretty general - however are you guys going to want to do anything
more fancy with these things?
Nick
next prev parent reply other threads:[~2004-08-14 3:23 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 [this message]
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
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=411D85C3.4030808@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