From: Adam Kropelin <akropel1@rochester.rr.com>
To: Robert Love <rml@tech9.net>
Cc: "David S. Miller" <davem@redhat.com>,
akpm@zip.com.au, linux-kernel@vger.kernel.org
Subject: Re: [patch] CONFIG_NR_CPUS
Date: Thu, 6 Jun 2002 13:09:35 -0400 [thread overview]
Message-ID: <20020606170935.GA32506@www.kroptech.com> (raw)
In-Reply-To: <3CFF3504.1DCD24E7@zip.com.au> <20020606.031520.08940800.davem@redhat.com> <1023377213.13787.2.camel@sinai>
On Thu, Jun 06, 2002 at 08:26:52AM -0700, Robert Love wrote:
> I have attached a patch that is Andrew's + your request, Dave. Since
> what really determines the maximum number of CPUs is the size of
> unsigned long, I used that. Cool?
>
> Robert Love
>
> diff -urN linux-2.5.20/arch/i386/Config.help linux/arch/i386/Config.help
> --- linux-2.5.20/arch/i386/Config.help Sun Jun 2 18:44:41 2002
> +++ linux/arch/i386/Config.help Thu Jun 6 07:58:58 2002
> @@ -25,6 +25,14 @@
>
> If you don't know what to do here, say N.
>
> +CONFIG_NR_CPUS
> + This allows you to specify the maximum number of CPUs which this
> + kernel will support. The maximum supported value is 32 and the
^^
This isn't quite true now...
--Adam
next prev parent reply other threads:[~2002-06-06 17:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 10:10 Andrew Morton
2002-06-06 10:15 ` David S. Miller
2002-06-06 15:26 ` Robert Love
2002-06-06 17:05 ` Tom Rini
2002-06-06 17:09 ` Adam Kropelin [this message]
2002-06-06 17:52 ` Robert Love
2002-06-06 19:48 ` Andrew Morton
2002-06-06 20:55 ` Andreas Dilger
2002-06-06 21:04 ` Andrew Morton
2002-06-06 21:23 ` Thomas 'Dent' Mirlacher
2002-06-06 21:36 ` Dave Jones
2002-06-06 21:49 ` Thomas 'Dent' Mirlacher
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=20020606170935.GA32506@www.kroptech.com \
--to=akropel1@rochester.rr.com \
--cc=akpm@zip.com.au \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.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®