[tip:x86/urgent] x86: Increase CONFIG_NODES_SHIFT max to 10

From: tip-bot for David Rientjes
Date: Fri Apr 02 2010 - 15:07:16 EST


Commit-ID: 51591e31dcb3716f03f962e26ec36a029aa46340
Gitweb: http://git.kernel.org/tip/51591e31dcb3716f03f962e26ec36a029aa46340
Author: David Rientjes <rientjes@xxxxxxxxxx>
AuthorDate: Thu, 25 Mar 2010 15:39:27 -0700
Committer: Ingo Molnar <mingo@xxxxxxx>
CommitDate: Fri, 2 Apr 2010 19:09:31 +0200

x86: Increase CONFIG_NODES_SHIFT max to 10

Some larger systems require more than 512 nodes, so increase the
maximum CONFIG_NODES_SHIFT to 10 for a new max of 1024 nodes.

This was tested with numa=fake=64M on systems with more than
64GB of RAM. A total of 1022 nodes were initialized.

Successfully builds with no additional warnings on x86_64
allyesconfig.

( No effect on any existing config. Newly enabled CONFIG_MAXSMP=y
will see the new default. )

Signed-off-by: David Rientjes <rientjes@xxxxxxxxxx>
LKML-Reference: <alpine.DEB.2.00.1003251538060.8589@xxxxxxxxxxxxxxxxxxxxxxxxx>
Signed-off-by: Ingo Molnar <mingo@xxxxxxx>
---
arch/x86/Kconfig | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
index 0eacb1f..9458685 100644
--- a/arch/x86/Kconfig
+++ b/arch/x86/Kconfig
@@ -1216,8 +1216,8 @@ config NUMA_EMU

config NODES_SHIFT
int "Maximum NUMA Nodes (as a power of 2)" if !MAXSMP
- range 1 9
- default "9" if MAXSMP
+ range 1 10
+ default "10" if MAXSMP
default "6" if X86_64
default "4" if X86_NUMAQ
default "3"
--
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/