kthread: use N_MEMORY instead N_HIGH_MEMORY
authorLai Jiangshan <laijs@cn.fujitsu.com>
Wed, 12 Dec 2012 21:51:39 +0000 (13:51 -0800)
committerLinus Torvalds <torvalds@linux-foundation.org>
Thu, 13 Dec 2012 01:38:33 +0000 (17:38 -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>
Signed-off-by: Wen Congyang <wency@cn.fujitsu.com>
Cc: Christoph Lameter <cl@linux.com>
Cc: Hillf Danton <dhillf@gmail.com>
Cc: Lin Feng <linfeng@cn.fujitsu.com>
Cc: David Rientjes <rientjes@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

index 29fb60caecb53125fa76e852609d38f4380cab4c..691dc2ef9baf241c121144799360a7e1237afcb5 100644 (file)
@@ -428,7 +428,7 @@ int kthreadd(void *unused)
        set_task_comm(tsk, "kthreadd");
        set_cpus_allowed_ptr(tsk, cpu_all_mask);
-       set_mems_allowed(node_states[N_HIGH_MEMORY]);
+       set_mems_allowed(node_states[N_MEMORY]);
        current->flags |= PF_NOFREEZE;