From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Frank A. Kingswood" <frank@kingswood-consulting.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NR_CPUS configuration option wrong
Date: Thu, 20 May 2010 10:38:51 -0700 [thread overview]
Message-ID: <20100520103851.8e051a3f.randy.dunlap@oracle.com> (raw)
In-Reply-To: <ht3rr8$b5f$2@dough.gmane.org>
On Thu, 20 May 2010 18:34:32 +0100 Frank A. Kingswood wrote:
> Hi!
>
> The configuration MAXSMP help text indicates it is used to enable
> configuration of number of CPUs. However, NR_CPUS depends on !MAXSMP.
>
> arch/x86/Kconfig:
> 758 config NR_CPUS
> 759 int "Maximum number of CPUs" if SMP && !MAXSMP
That line depends on !MAXSMP. Then below there, we find:
default "4096" if MAXSMP
OK?
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-05-20 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-20 17:34 NR_CPUS configuration option wrong Frank A. Kingswood
2010-05-20 17:38 ` Randy Dunlap [this message]
2010-05-20 18:32 ` Frank A. Kingswood
2010-05-20 18:35 ` Randy Dunlap
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=20100520103851.8e051a3f.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=frank@kingswood-consulting.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).