summaryrefslogtreecommitdiff
path: root/fs
diff options
context:
space:
mode:
authorYinghai Lu <yinghai@kernel.org>2009-05-15 20:59:37 (GMT)
committerIngo Molnar <mingo@elte.hu>2009-05-18 07:21:04 (GMT)
commit7c43769a9776141ec23ca81a1bdd5a9c0512f165 (patch)
treee24d99a84d76386b0bf910152d1841853857e63f /fs
parent888a589f6be07d624e21e2174d98375e9f95911b (diff)
downloadlinux-7c43769a9776141ec23ca81a1bdd5a9c0512f165.tar.xz
x86, mm: Fix node_possible_map logic
Recently there were some changes to the meaning of node_possible_map, and it is quite strange: - the node without memory would be set in node_possible_map - but some node with less NODE_MIN_SIZE will be kicked out of node_possible_map. fix it by adding strict_setup_node_bootmem(). Also, remove unparse_node(). so result will be: 1. cpu_to_node() will return online node only (nearest one) 2. apicid_to_node() still returns the node that could be not online but is set in node_possible_map. 3. node_possible_map will include nodes that mem on it are less NODE_MIN_SIZE v2: after move_cpus_to_node change. [ Impact: get node_possible_map right ] Signed-off-by: Yinghai Lu <yinghai@kernel.org> Tested-by: Jack Steiner <steiner@sgi.com> LKML-Reference: <4A0C49BE.6080800@kernel.org> [ v3: various small cleanups and comment clarifications ] Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'fs')
0 files changed, 0 insertions, 0 deletions