On Tue, 8 Jun 2010, KOSAKI Motohiro wrote: > > @@ -267,6 +259,8 @@ static struct task_struct *select_bad_process(unsigned long *ppoints, > > continue; > > if (mem && !task_in_mem_cgroup(p, mem)) > > continue; > > + if (!has_intersects_mems_allowed(p)) > > + continue; > > > > /* > > * This task already has access to memory reserves and is > > now we have three places of oom filtering > (1) select_bad_process Done. > (2) dump_tasks dump_tasks() has never filtered on this, it's possible for tasks is other cpusets to allocate memory on our nodes. > (3) oom_kill_task (when oom_kill_allocating_task==1 only) > Why would care about cpuset attachment in oom_kill_task()? You mean oom_kill_process() to filter the children list? -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>