| Date | Wed, 10 Feb 2010 12:08:45 -0500 | From | Rik van Riel <> | Subject | Re: [patch 1/7 -mm] oom: filter tasks not sharing the same cpuset |
| |
On 02/10/2010 11:32 AM, David Rientjes wrote: > Tasks that do not share the same set of allowed nodes with the task that > triggered the oom should not be considered as candidates for oom kill. > > Tasks in other cpusets with a disjoint set of mems would be unfairly > penalized otherwise because of oom conditions elsewhere; an extreme > example could unfairly kill all other applications on the system if a > single task in a user's cpuset sets itself to OOM_DISABLE and then uses > more memory than allowed. > > Killing tasks outside of current's cpuset rarely would free memory for > current anyway. > > Signed-off-by: David Rientjes<rientjes@google.com>
Acked-by: Rik van Riel <riel@redhat.com>
-- All rights reversed.
|