x86-32, numa: Calculate remap size in common code
authorTejun Heo <tj@kernel.org>
Mon, 4 Apr 2011 22:23:53 +0000 (00:23 +0200)
committerH. Peter Anvin <hpa@zytor.com>
Thu, 7 Apr 2011 00:57:16 +0000 (17:57 -0700)
commit7210cf9217937e470a9acbc113a590f476b9c047
tree7d253d9d701e54710b0d26c67a38b67e860e6a2a
parentaf7c1a6e8374e05aab4a98ce4d2fb07b66506a02
x86-32, numa: Calculate remap size in common code

Only pgdat and memmap use remap area and there isn't much benefit in
allowing per-node override.  In addition, the use of node_remap_size[]
is confusing in that it contains number of bytes before remap
initialization and then number of pages afterwards.

Move remap size calculation for memap from specific NUMA config
implementations to init_alloc_remap() and make node_remap_size[]
static.

The only behavior difference is that, before this patch, numaq_32
didn't consider max_pfn when calculating the memmap size but it's
enforced after this patch, which is the right thing to do.

Signed-off-by: Tejun Heo <tj@kernel.org>
Link: http://lkml.kernel.org/r/1301955840-7246-8-git-send-email-tj@kernel.org
Acked-by: Yinghai Lu <yinghai@kernel.org>
Cc: David Rientjes <rientjes@google.com>
Signed-off-by: H. Peter Anvin <hpa@zytor.com>
arch/x86/include/asm/topology.h
arch/x86/kernel/apic/numaq_32.c
arch/x86/mm/numa_32.c
arch/x86/mm/srat_32.c