From: Matthew Dobson <colpatch@us.ibm.com>
To: Andrew Morton <akpm@osdl.org>
Cc: nickpiggin@yahoo.com.au, LKML <linux-kernel@vger.kernel.org>,
"Martin J. Bligh" <mbligh@aracnet.com>, Andi Kleen <ak@suse.de>
Subject: Re: [RFC PATCH] sched_domains: Make SD_NODE_INIT per-arch
Date: Thu, 30 Sep 2004 13:20:25 -0700 [thread overview]
Message-ID: <1096575625.20097.25.camel@arrakis> (raw)
In-Reply-To: <20040930122312.3f09ed73.akpm@osdl.org>
On Thu, 2004-09-30 at 12:23, Andrew Morton wrote:
> 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.
Yeah, that's entirely my fault for slacking on sending this out... I
should have sent this a while ago. It is a small portion of some larger
sched_domains changes that I am working on, but at some point I realized
my larger changeset will be far more controversial and have a much
larger impact than some of the smaller bits, as well as not being ready
for prime time yet. Plus, like I said earlier, this allows
arch-specific tweaking with minimal intrusiveness from the application
of this patch forward.
> 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.
It *should* be. I'd be quite happy if you just picked it up in -mm to
assure it far wider testing. I've compiled and booted it on x86, x86_64
& ppc64. I've got no access to ia64 right now, or I'd test it there.
But the patch *will* spit out #errors for any arch that doesn't have
SD_NODE_INIT defined if they also have NUMA defined. I'm don't know of
anyone else (ie: *not* x86, x86_64, ppc64 & ia64) that is building NUMA
kernels, but if they are, it's a trivial patch to their
include/asm/topology.h to make the arch build.
Of course, the ultimate decision is yours, Andrew...
-Matt
next prev parent reply other threads:[~2004-09-30 20:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-29 1:12 [RFC PATCH] sched_domains: Make SD_NODE_INIT per-arch 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 [this message]
2004-10-01 6:15 ` Martin J. Bligh
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=1096575625.20097.25.camel@arrakis \
--to=colpatch@us.ibm.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
--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