From: Matthew Wilcox <matthew@wil.cx>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
hawkes@sgi.com, Tony Luck <tony.luck@gmail.com>,
Andrew Morton <akpm@osdl.org>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
Jack Steiner <steiner@sgi.com>, Dan Higgins <djh@sgi.com>,
John Hesterberg <jh@sgi.com>, Greg Edwards <edwardsg@sgi.com>
Subject: Re: [PATCH] ia64: change defconfig to NR_CPUS==1024
Date: Fri, 06 Jan 2006 17:26:15 +0000 [thread overview]
Message-ID: <20060106172615.GE19769@parisc-linux.org> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F055A7AFB@scsmsx401.amr.corp.intel.com>
On Fri, Jan 06, 2006 at 09:19:28AM -0800, Luck, Tony wrote:
> Would it be impossibly hard to make the >64 cpus case (when the code
> switches from a single word to an array) be dependent on a boot-time
> variable? If we could, then the defconfig could just say 128, and
> users of monster machines would just boot with "maxcpus@96" to increase
> the size of the bitmask arrays.
Why can't we keep the default below 64? Surely the 0.1% of the market
which needs more than 64 cpus can recompile their kernel ...
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Wilcox <matthew@wil.cx>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
hawkes@sgi.com, Tony Luck <tony.luck@gmail.com>,
Andrew Morton <akpm@osdl.org>,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
Jack Steiner <steiner@sgi.com>, Dan Higgins <djh@sgi.com>,
John Hesterberg <jh@sgi.com>, Greg Edwards <edwardsg@sgi.com>
Subject: Re: [PATCH] ia64: change defconfig to NR_CPUS==1024
Date: Fri, 6 Jan 2006 10:26:15 -0700 [thread overview]
Message-ID: <20060106172615.GE19769@parisc-linux.org> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F055A7AFB@scsmsx401.amr.corp.intel.com>
On Fri, Jan 06, 2006 at 09:19:28AM -0800, Luck, Tony wrote:
> Would it be impossibly hard to make the >64 cpus case (when the code
> switches from a single word to an array) be dependent on a boot-time
> variable? If we could, then the defconfig could just say 128, and
> users of monster machines would just boot with "maxcpus=4096" to increase
> the size of the bitmask arrays.
Why can't we keep the default below 64? Surely the 0.1% of the market
which needs more than 64 cpus can recompile their kernel ...
next prev parent reply other threads:[~2006-01-06 17:26 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 21:39 [PATCH] ia64: change defconfig to NR_CPUS==1024 hawkes
2006-01-05 21:39 ` hawkes
2006-01-05 22:33 ` Chen, Kenneth W
2006-01-05 22:33 ` Chen, Kenneth W
2006-01-06 17:06 ` John Hawkes
2006-01-06 17:06 ` John Hawkes
2006-01-06 8:38 ` Arjan van de Ven
2006-01-06 8:38 ` Arjan van de Ven
2006-01-06 17:19 ` Luck, Tony
2006-01-06 17:19 ` Luck, Tony
2006-01-06 17:24 ` Arjan van de Ven
2006-01-06 17:24 ` Arjan van de Ven
2006-01-06 17:26 ` Matthew Wilcox [this message]
2006-01-06 17:26 ` Matthew Wilcox
2006-01-06 17:45 ` Luck, Tony
2006-01-06 17:45 ` Luck, Tony
2006-01-06 17:49 ` Matthew Wilcox
2006-01-06 17:49 ` Matthew Wilcox
2006-01-06 18:04 ` Christoph Lameter
2006-01-06 18:04 ` Christoph Lameter
2006-01-06 18:07 ` Matthew Wilcox
2006-01-06 18:07 ` Matthew Wilcox
2006-01-06 18:19 ` Randy.Dunlap
2006-01-06 18:19 ` Randy.Dunlap
2006-01-06 18:37 ` Christoph Lameter
2006-01-06 18:37 ` Christoph Lameter
2006-01-06 18:59 ` Arjan van de Ven
2006-01-06 18:59 ` Arjan van de Ven
2006-01-06 20:17 ` Alan Cox
2006-01-06 20:18 ` Randy.Dunlap
2006-01-06 20:18 ` Randy.Dunlap
2006-01-06 20:42 ` Rohit Seth
2006-01-06 20:42 ` Rohit Seth
2006-01-06 21:00 ` Dave Jones
2006-01-06 21:00 ` Dave Jones
2006-01-06 18:25 ` Adrian Bunk
2006-01-06 18:25 ` Adrian Bunk
2006-01-12 0:09 ` Paul Jackson
2006-01-12 0:09 ` Paul Jackson
2006-01-12 19:04 ` Christoph Lameter
2006-01-12 19:04 ` Christoph Lameter
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=20060106172615.GE19769@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=djh@sgi.com \
--cc=edwardsg@sgi.com \
--cc=hawkes@sgi.com \
--cc=jh@sgi.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
--cc=tony.luck@gmail.com \
--cc=tony.luck@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.