* [PATCH 2/5] mm/sparse: use N_MEMORY instead of N_HIGH_MEMORY
@ 2013-08-30 3:38 Jianguo Wu
0 siblings, 0 replies; only message in thread
From: Jianguo Wu @ 2013-08-30 3:38 UTC (permalink / raw)
To: Andrew Morton, laijs; +Cc: Wen Congyang, Tang Chen, linux-mm, linux-kernel
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 <wujianguo@huawei.com>
---
mm/sparse.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/mm/sparse.c b/mm/sparse.c
index 308d503..8519d6a 100644
--- a/mm/sparse.c
+++ b/mm/sparse.c
@@ -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);
--
1.7.1
^ permalink raw reply related [flat|nested] only message in thread
only message in thread, other threads:[~2013-08-30 3:38 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-08-30 3:38 [PATCH 2/5] mm/sparse: use N_MEMORY instead of N_HIGH_MEMORY Jianguo Wu
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).