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
Date: Thu, 30 Sep 2004 23:15:31 -0700 [thread overview]
Message-ID: <78560000.1096611330@[10.10.2.4]> (raw)
In-Reply-To: <20040930122312.3f09ed73.akpm@osdl.org>
--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.
next prev parent reply other threads:[~2004-10-01 6:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 1:12 Matthew Dobson
2004-09-30 8:15 ` Nick Piggin
2004-09-30 18:36 ` Matthew Dobson
2004-09-30 19:23 ` Andrew Morton
2004-09-30 20:20 ` Matthew Dobson
2004-10-01 6:15 ` Martin J. Bligh [this message]
2004-10-01 22:20 ` Matthew Dobson
2004-10-02 16:02 ` Martin J. Bligh
2004-09-30 20:45 ` Andi Kleen
2004-09-30 21:06 ` Matthew Dobson
2004-09-30 21:12 ` Andi Kleen
2004-09-30 23:47 ` Matthew Dobson
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='78560000.1096611330@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=colpatch@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
/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
all inboxes | Powered by JetHome®