From: Jack Steiner <steiner@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: ak@suse.de, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] - Allow NODES_SHIFT to be a config option on x86_64
Date: Fri, 21 Mar 2008 10:23:05 -0500 [thread overview]
Message-ID: <20080321152305.GA28098@sgi.com> (raw)
In-Reply-To: <20080321145736.GC1545@elte.hu>
On Fri, Mar 21, 2008 at 03:57:36PM +0100, Ingo Molnar wrote:
>
> * Jack Steiner <steiner@sgi.com> wrote:
>
> > On Fri, Mar 21, 2008 at 03:26:49PM +0100, Ingo Molnar wrote:
> > >
> > > * Jack Steiner <steiner@sgi.com> wrote:
> > >
> > > > Allow the maximum number of nodes in an x86_64 system to be
> > > > configurable. This patch does NOT change the default value but allows
> > > > the value to be a config option.
> > >
> > > i've applied your patch - but i'm wondering, shouldnt we auto-scale the
> > > default according to max number of CPUs? (with some sensible scaling
> > > that happens to meet your expected large-system needs as well ;-) All
> > > the current manual configuration of nodes shift is ugly.
> >
> > I would prefer to auto-scale, too, but our hardware platform allows
> > too many options to make it easy. The current system configs will
> > support from 0 to 32 cpus per node (some nodes have memory only).
> >
> > However, I'm open to suggestions if you have any ideas....
>
> how about scaling for the worst case, and allowing distros to tune down
> if they really want? What's the cost of a too large NODE_SHIFT?
>
NODE_SHIFT affects a number of nodemasks so you probably don't want it
a lot larger than needed - especially if you are going over 64 nodes. Our
target value is currently 512 although it is possible that it may
change to 256.
Let me do some experiments on auto-config. I'll get back to you....
--- jack
prev parent reply other threads:[~2008-03-21 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 13:34 [PATCH] - Allow NODES_SHIFT to be a config option on x86_64 Jack Steiner
2008-03-21 14:26 ` Ingo Molnar
2008-03-21 14:54 ` Jack Steiner
2008-03-21 14:57 ` Ingo Molnar
2008-03-21 15:23 ` Jack Steiner [this message]
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=20080321152305.GA28098@sgi.com \
--to=steiner@sgi.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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