From: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
To: Robert Love <rml@tech9.net>,
Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
linux-kernel@vger.kernel.org, akpm@zip.com.au
Subject: Re: [PATCH] CONFIG_NR_CPUS, redux
Date: Wed, 12 Jun 2002 08:06:58 -0700 [thread overview]
Message-ID: <3215445436.1023869217@[10.10.2.3]> (raw)
In-Reply-To: <1023820116.22156.271.camel@sinai>
> Ugh let's stop this thread now. Two points:
>
> (a) imo, the kernel should support out-of-the-box the maximum
> number of CPUs it can handle. Be lucky we now have a
> configure option to change that. But that does not matter..
>
> (b) Right now it is 32. Now you can change it... if you want
> to change the current behavior by _default_ why don't we
> suggest that _after_ this is accepted into 2.5? I.e., one
> battle at a time.
Indeed. And before that gets changed, it would be necessary
to change the bootstrap procedure not to crash if you have
more than NR_CPUS cpus (as Andrew reported it did), but instead
to just not configure them ... much less troublesome.
M.
next prev parent reply other threads:[~2002-06-12 15:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 17:52 Robert Love
2002-06-11 18:09 ` Randy.Dunlap
2002-06-11 18:19 ` Robert Love
2002-06-11 18:21 ` Ruth Ivimey-Cook
2002-06-11 18:28 ` Robert Love
2002-06-12 1:36 ` jw schultz
2002-06-12 15:06 ` Martin J. Bligh [this message]
2002-06-12 15:22 ` William Lee Irwin III
2002-06-11 18:29 ` Martin Dalecki
2002-06-11 23:20 ` Dave Jones
2002-06-13 8:51 ` Helge Hafting
2002-06-19 11:53 ` Bill Davidsen
2002-06-11 20:10 ` Rob Radez
2002-06-12 3:29 Matt_Domsch
2002-06-12 4:13 ` Austin Gonyou
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='3215445436.1023869217@[10.10.2.3]' \
--to=martin.bligh@us.ibm.com \
--cc=Ruth.Ivimey-Cook@ivimey.org \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.org \
--cc=rml@tech9.net \
/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®