Re: [patch 2/4] mm, oom: cleanup pagefault oom handler

2012-11-15 Thread David Rientjes
On Thu, 15 Nov 2012, Kamezawa Hiroyuki wrote: > > @@ -708,15 +671,17 @@ out: > > > > /* > >* The pagefault handler calls here because it is out of memory, so kill a > > - * memory-hogging task. If a populated zone has ZONE_OOM_LOCKED set, a > > parallel > > - * oom killing is already in

Re: [patch 2/4] mm, oom: cleanup pagefault oom handler

2012-11-15 Thread Michal Hocko
On Thu 15-11-12 17:45:18, KAMEZAWA Hiroyuki wrote: > (2012/11/14 18:15), David Rientjes wrote: [...] > >@@ -708,15 +671,17 @@ out: > > > > /* > > * The pagefault handler calls here because it is out of memory, so kill a > >- * memory-hogging task. If a populated zone has ZONE_OOM_LOCKED set, a

Re: [patch 2/4] mm, oom: cleanup pagefault oom handler

2012-11-15 Thread Kamezawa Hiroyuki
(2012/11/14 18:15), David Rientjes wrote: To lock the entire system from parallel oom killing, it's possible to pass in a zonelist with all zones rather than using for_each_populated_zone() for the iteration. This obsoletes try_set_system_oom() and clear_system_oom() so that they can be

Re: [patch 2/4] mm, oom: cleanup pagefault oom handler

2012-11-15 Thread Kamezawa Hiroyuki
(2012/11/14 18:15), David Rientjes wrote: To lock the entire system from parallel oom killing, it's possible to pass in a zonelist with all zones rather than using for_each_populated_zone() for the iteration. This obsoletes try_set_system_oom() and clear_system_oom() so that they can be

Re: [patch 2/4] mm, oom: cleanup pagefault oom handler

2012-11-15 Thread Michal Hocko
On Thu 15-11-12 17:45:18, KAMEZAWA Hiroyuki wrote: (2012/11/14 18:15), David Rientjes wrote: [...] @@ -708,15 +671,17 @@ out: /* * The pagefault handler calls here because it is out of memory, so kill a - * memory-hogging task. If a populated zone has ZONE_OOM_LOCKED set, a parallel

Re: [patch 2/4] mm, oom: cleanup pagefault oom handler

2012-11-15 Thread David Rientjes
On Thu, 15 Nov 2012, Kamezawa Hiroyuki wrote: @@ -708,15 +671,17 @@ out: /* * The pagefault handler calls here because it is out of memory, so kill a - * memory-hogging task. If a populated zone has ZONE_OOM_LOCKED set, a parallel - * oom killing is already in progress so do

Re: [patch 2/4] mm, oom: cleanup pagefault oom handler

2012-11-14 Thread Michal Hocko
On Wed 14-11-12 01:15:22, David Rientjes wrote: > To lock the entire system from parallel oom killing, it's possible to > pass in a zonelist with all zones rather than using > for_each_populated_zone() for the iteration. This obsoletes > try_set_system_oom() and clear_system_oom() so that they

[patch 2/4] mm, oom: cleanup pagefault oom handler

2012-11-14 Thread David Rientjes
To lock the entire system from parallel oom killing, it's possible to pass in a zonelist with all zones rather than using for_each_populated_zone() for the iteration. This obsoletes try_set_system_oom() and clear_system_oom() so that they can be removed. Cc: KAMEZAWA Hiroyuki Cc: KOSAKI

[patch 2/4] mm, oom: cleanup pagefault oom handler

2012-11-14 Thread David Rientjes
To lock the entire system from parallel oom killing, it's possible to pass in a zonelist with all zones rather than using for_each_populated_zone() for the iteration. This obsoletes try_set_system_oom() and clear_system_oom() so that they can be removed. Cc: KAMEZAWA Hiroyuki

Re: [patch 2/4] mm, oom: cleanup pagefault oom handler

2012-11-14 Thread Michal Hocko
On Wed 14-11-12 01:15:22, David Rientjes wrote: To lock the entire system from parallel oom killing, it's possible to pass in a zonelist with all zones rather than using for_each_populated_zone() for the iteration. This obsoletes try_set_system_oom() and clear_system_oom() so that they can be