linux-kernel - Re: NR_CPUS configuration option wrong

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4BF58054.8060601@kingswood-consulting.co.uk>
Date:	Thu, 20 May 2010 19:32:52 +0100
From:	"Frank A. Kingswood" <frank@...gswood-consulting.co.uk>
To:	Randy Dunlap <randy.dunlap@...cle.com>
CC:	linux-kernel@...r.kernel.org
Subject: Re: NR_CPUS configuration option wrong

Randy Dunlap wrote:
> 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

Hah, weird.
I can see now it is possible to parse the MAXSMP help this way, but it 
was not obvious.

In menuconfig you see two questions:

[ ] Configure Maximum number of SMP Processors and NUMA Nodes
[8] Maximum number of CPUs

and setting the first one YES makes the second one go away.

Perhaps restating the help as "Set number of SMP processors and NUMA 
nodes to the maximum that the kernel supports" might help.

Thanks,

Frank
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/