mm/sparse: use N_MEMORY instead of N_HIGH_MEMORY
Subsystems (2)
PATCH 2/5 mm/sparse: use N_MEMORY instead of N_HIGH_MEMORY
Since commit 8219fc48a(mm: node_states: introduce N_MEMORY),
we introduced N_MEMORY, now N_MEMORY stands for the nodes that has any memory, and N_HIGH_MEMORY stands for the nodes that has normal or high memory.
The code here need to handle with the nodes which have memory, we should use N_MEMORY instead.
Signed-off-by Jianguo Wu <[email protected]>
--- mm/sparse.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
mm/sparse.c +1 -1
@@ -64,7 +64,7 @@ static struct mem_section noinline __init_refok *sparse_index_alloc(int nid)sizeof (struct mem_section );if (slab_is_available ()) { -if (node_state (nid,N_HIGH_MEMORY )) +if (node_state (nid,N_MEMORY )) section =kzalloc_node (array_size,GFP_KERNEL , nid);else section =kzalloc (array_size,GFP_KERNEL );
Signature · 8 lines
1.7.1 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"[email protected]"> [email protected] </a>