From: Helge Hafting <helgehaf@aitel.hist.no>
To: Ruth Ivimey-Cook <Ruth.Ivimey-Cook@ivimey.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CONFIG_NR_CPUS, redux
Date: Thu, 13 Jun 2002 10:51:19 +0200 [thread overview]
Message-ID: <3D085D07.4DC40FF3@aitel.hist.no> (raw)
In-Reply-To: <Pine.LNX.4.44.0206111917310.3521-100000@sharra.ivimey.org>
Ruth Ivimey-Cook wrote:
> Perhaps it's just because I'm coming in late, but I cannot understand why
> NR_CPUS cannot be as low as 4 by default, for all archs, and then in the
> kernel boot messages, should more be found than is configured for a message is
> emitted to say "reconfigure your kernel", and continue with the number it was
> configured for. I personally only rarely see 2-way boxes, 4-way is pretty
> rare, and anything more must surely count as very specialized.
>
Why not let the boot process select the highest of two numbers,
the (default-low) NR_CPUS and the number of CPU's detected?
Boot with "too many" cpu's and you still get to use them - you
merely can't hotplug even more.
Configuring a high NR_CPUS becomes something only hot-pluggers
need to do, or those whose architecture doesn't support
cpu detection in the early boot process. Those with a fixed
number of detectable CPUs can simply go with a default of
NR_CPUS=2 no matter what they actually have.
Helge Hafting
next prev parent reply other threads:[~2002-06-13 8:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-11 17:52 [PATCH] CONFIG_NR_CPUS, redux 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
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 [this message]
2002-06-19 11:53 ` Bill Davidsen
2002-06-11 20:10 ` Rob Radez
-- strict thread matches above, loose matches on Subject: below --
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=3D085D07.4DC40FF3@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=Ruth.Ivimey-Cook@ivimey.org \
--cc=linux-kernel@vger.kernel.org \
/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