[V4 PATCH 16/26] vmscan: use N_MEMORY instead N_HIGH_MEMORY

Lai Jiangshan
2012-09-10T09:04:53Z

N_HIGH_MEMORY stands for the nodes that has normal or high memory.
N_MEMORY stands for the nodes that has any memory.

The code here need to handle with the nodes which have memory, we should
use N_MEMORY instead.

Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
Acked-by: Hillf Danton <dhillf@gmail.com>
---
mm/vmscan.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/mm/vmscan.c b/mm/vmscan.c
index 8d01243..cb42747 100644
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -3071,7 +3071,7 @@ static int __devinit cpu_callback(struct notifier_block *nfb,
int nid;

if (action == CPU_ONLINE || action == CPU_ONLINE_FROZEN) {
- for_each_node_state(nid, N_HIGH_MEMORY) {
+ for_each_node_state(nid, N_MEMORY) {
pg_data_t *pgdat = NODE_DATA(nid);
const struct cpumask *mask;

@@ -3126,7 +3126,7 @@ static int __init kswapd_init(void)
int nid;

swap_setup();
- for_each_node_state(nid, N_HIGH_MEMORY)
+ for_each_node_state(nid, N_MEMORY)
kswapd_run(nid);
hotcpu_notifier(cpu_callback, 0);
return 0;
--
1.7.1