public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: colpatch@us.ibm.com
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>,
	"Martin J. Bligh" <mbligh@aracnet.com>
Subject: Re: [RFC PATCH] sched_domains: Make SD_NODE_INIT per-arch
Date: Thu, 30 Sep 2004 18:15:56 +1000	[thread overview]
Message-ID: <415BC0BC.6040902@yahoo.com.au> (raw)
In-Reply-To: <1096420339.15060.139.camel@arrakis>

Matthew Dobson wrote:
> IA64 already has their own version of SD_NODE_INIT, tuned for their
> extremely large machines.  I think that all arches would benefit from
> having their own, arch-specific SD_NODE_INIT initializer, rather than
> the one-size-fits-all variant we've got now.
> 

I suppose the patch is pretty good (IIRC Martin liked the idea).
I guess it will at least increase the incidence of copy+paste,
if not getting people to think harder ;)

Can I be lame and ask that you keep this around until closer
to 2.6.10? I have a few possible scheduler performance
improvments that I'd like to get tested in -mm after 2.6.9
and this would make things a bit harder :P

I don't think anyone is looking at getting any tweaks in before
then...

  reply	other threads:[~2004-09-30  8:16 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 [this message]
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
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=415BC0BC.6040902@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=colpatch@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbligh@aracnet.com \
    /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