Date: Thu, 30 Sep 2004 23:15:31 -0700
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andrew Morton <akpm@osdl.org>, colpatch@us.ibm.com
cc: nickpiggin@yahoo.com.au, linux-kernel@vger.kernel.org, ak@suse.de
Subject: Re: [RFC PATCH] sched_domains: Make SD_NODE_INIT per-arch
Message-ID: <78560000.1096611330@[10.10.2.4]>
In-Reply-To: <20040930122312.3f09ed73.akpm@osdl.org>
References: <1096420339.15060.139.camel@arrakis><415BC0BC.6040902@yahoo.com.au><1096569412.20097.13.camel@arrakis> <20040930122312.3f09ed73.akpm@osdl.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1296
Lines: 31

--Andrew Morton <akpm@osdl.org> wrote (on Thursday, September 30, 2004 12:23:12 -0700):

> Matthew Dobson <colpatch@us.ibm.com> wrote:
>> 
>> I would like to try to get this in before then, unless this will really
>>  make things difficult for you.
> 
> It's about three weeks late for 2.6.9.  I already have a string of CPU
> scheduler patches awaiting the 2.6.10 stream and once we're at -rc2 we
> really should only be looking at bugfixes.

Yup, seems a bit late for that, but early 2.6.10 would be nice if possible?
 
> Grumble, mutter..  it looks like one of those "if it compiled, it works"
> things.  Problem is, any time anyone touches that particular piece of the
> kernel, half the architectures stop compiing.

I tested it - worked for me ;-)

This is the first step to getting the arches to actually use the flexibility
we had, and stop Andi complaining the scheduler is tuned for one arch rather
than another ;-) These params definitely need to be per arch/subarch, and
probably some other ones too, but this seems like a good start.

M.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/