| From | Lai Jiangshan <> | Subject | [RFC PATCH 12/23 V2] vmscan: use N_MEMORY instead N_HIGH_MEMORY | Date | Thu, 2 Aug 2012 14:01:17 +0800 |
| |
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> --- mm/vmscan.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/mm/vmscan.c b/mm/vmscan.c index 66e4310..1888026 100644 --- a/mm/vmscan.c +++ b/mm/vmscan.c @@ -2921,7 +2921,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; @@ -2976,7 +2976,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
|