CONFIG_NR_CPUS limit for 32-bit

From: Jan Beulich
Date: Fri Aug 22 2008 - 10:35:55 EST


Given that the fixmap area size depends on NR_CPUS and that it can't
possibly cover 4096 CPUs (its size would be beyond 200Mb if I put things
together correctly, whereas the vmalloc area [of which the fixmap area is
a sub-portion] by default is 128MB) I can't see how this new limit ought to
even boot on any system.

Therefore I wonder whether the range shouldn't be restricted for X86_32.

Jan

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