public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: jw schultz <jw@pegasys.ws>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CONFIG_NR_CPUS, redux
Date: Tue, 11 Jun 2002 18:36:16 -0700	[thread overview]
Message-ID: <20020611183616.H856@pegasys.ws> (raw)
In-Reply-To: <Pine.LNX.4.44.0206111917310.3521-100000@sharra.ivimey.org> <1023820116.22156.271.camel@sinai>

On Tue, Jun 11, 2002 at 11:28:36AM -0700, Robert Love wrote:
> On Tue, 2002-06-11 at 11:21, 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.
> 
> 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.

By that logic CONFIG_SMP should be "y" by default.

Now i find the name NR_CPUS a bit misleading it seems that
this should be MAX_CPUS but "legacy is as legacy does".

Using the names i prefer i would suggest in *config we
replace CONFIG_SMP with CONFIG_MAX_CPUS and give it a
default of 1.  Then make CONFIG_SMP dependant on
CONFIG_MAX_CPUS > 1.  That way we avoid adding yet another
option. KISS for the users.

-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt

  reply	other threads:[~2002-06-12  1:36 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 [this message]
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
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=20020611183616.H856@pegasys.ws \
    --to=jw@pegasys.ws \
    --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