From: Ingo Molnar <mingo@elte.hu>
To: Jack Steiner <steiner@sgi.com>
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 15:26:49 +0100 [thread overview]
Message-ID: <20080321142648.GB31719@elte.hu> (raw)
In-Reply-To: <20080321133425.GA11095@sgi.com>
* 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.
Ingo
next prev parent reply other threads:[~2008-03-21 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-21 13:34 Jack Steiner
2008-03-21 14:26 ` Ingo Molnar [this message]
2008-03-21 14:54 ` Jack Steiner
2008-03-21 14:57 ` Ingo Molnar
2008-03-21 15:23 ` Jack Steiner
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=20080321142648.GB31719@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
--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
all inboxes | Powered by JetHome®