From: Arjan van de Ven <arjan@infradead.org>
To: hawkes@sgi.com
Cc: 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 08:38:18 +0000 [thread overview]
Message-ID: <1136536698.2940.5.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060105213948.11412.45463.sendpatchset@tomahawk.engr.sgi.com>
On Thu, 2006-01-05 at 13:39 -0800, hawkes@sgi.com wrote:
> Increase the generic ia64 config from its current max of 512 CPUs to a
> new max of 1024 CPUs.
I wonder why this would be seen as a sane thing...
Very few people have 1024 cpus, and the ones that do sure would know how
to set 1024 in their kernel config. In fact I would argue to lower it. I
can see the point of keeping it over 64, to give the
more-cpus-than-a-long code more testing, but 512 is too high already..
most people who have ia64 will not have 512 cpus.
(and please don't say "but distributions.." because distributions don't
use the defconfigs anyway)
next prev parent reply other threads:[~2006-01-06 8:38 UTC|newest]
Thread overview: 21+ 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 22:33 ` Chen, Kenneth W
2006-01-06 17:06 ` John Hawkes
2006-01-06 8:38 ` Arjan van de Ven [this message]
2006-01-06 17:19 ` Luck, Tony
2006-01-06 17:24 ` Arjan van de Ven
2006-01-06 17:26 ` Matthew Wilcox
2006-01-06 17:45 ` Luck, Tony
2006-01-06 17:49 ` Matthew Wilcox
2006-01-06 18:04 ` Christoph Lameter
2006-01-06 18:07 ` Matthew Wilcox
2006-01-06 18:19 ` Randy.Dunlap
2006-01-06 18:37 ` Christoph Lameter
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:42 ` Rohit Seth
2006-01-06 21:00 ` Dave Jones
2006-01-06 18:25 ` Adrian Bunk
2006-01-12 0:09 ` Paul Jackson
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=1136536698.2940.5.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=akpm@osdl.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 \
/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