From: Robert Love <rml@tech9.net>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org, akpm@zip.com.au
Subject: Re: [PATCH] CONFIG_NR_CPUS, redux
Date: 11 Jun 2002 11:19:34 -0700 [thread overview]
Message-ID: <1023819574.22156.258.camel@sinai> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0206111102110.2449-100000@dragon.pdx.osdl.net>
On Tue, 2002-06-11 at 11:09, Randy.Dunlap wrote:
> I don't know what is "typical" for non-x86, but for x86, why not
> use something more like a 'typical' NR_CPUS for SMP, like 8 (?)...
> why still waste all of that memory?
Well right now we set it to 32...
I think out-of-the-box Linux, with SMP set, should support the maximum
number of CPUs. While we do save some memory I do not think it is going
to be huge with 8 vs 32.
But whatever you, Linus, and the arch maintainers say... all my boxen
are 2-way so I don't care ;)
> What was this problem? I missed it but would like to see it.
> (or do you know what the Subject: was?)
Not sure to be honest. The subject was "[patch] CONFIG_NR_CPUS"
Or ask Andrew...
> One spello (typo) below.
>
> | + mimimum value which makes sense is 2.
(cough) someone else wrote that ;)
Fixed, thanks.
Robert Love
next prev parent reply other threads:[~2002-06-11 18:19 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 [this message]
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
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=1023819574.22156.258.camel@sinai \
--to=rml@tech9.net \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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