cpumask: make CONFIG_NR_CPUS always valid.

Impact: cleanup

Currently we have NR_CPUS, which is 1 on UP, and CONFIG_NR_CPUS on
SMP.  If we make CONFIG_NR_CPUS always valid (and always 1 on !SMP),
we can skip the middleman.

This also allows us to find and check all the unaudited NR_CPUS usage
as we prepare for v. large NR_CPUS.

To avoid breaking every arch, we cheat and do this for the moment
in the header if the arch doesn't.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Signed-off-by: Mike Travis <travis@sgi.com>
This commit is contained in:
Rusty Russell 2008-12-30 09:05:12 +10:30
parent 33edcf133b
commit 278d1ed65e

View file

@ -8,17 +8,17 @@
*/ */
/* /*
* Maximum supported processors that can run under SMP. This value is * Maximum supported processors. Setting this smaller saves quite a
* set via configure setting. The maximum is equal to the size of the * bit of memory. Use nr_cpu_ids instead of this except for static bitmaps.
* bitmasks used on that platform, i.e. 32 or 64. Setting this smaller
* saves quite a bit of memory.
*/ */
#ifdef CONFIG_SMP #ifndef CONFIG_NR_CPUS
#define NR_CPUS CONFIG_NR_CPUS /* FIXME: This should be fixed in the arch's Kconfig */
#else #define CONFIG_NR_CPUS 1
#define NR_CPUS 1
#endif #endif
/* Places which use this should consider cpumask_var_t. */
#define NR_CPUS CONFIG_NR_CPUS
#define MIN_THREADS_LEFT_FOR_ROOT 4 #define MIN_THREADS_LEFT_FOR_ROOT 4
/* /*