[lkml]   [2010]   [Feb]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch 1/7 -mm] oom: filter tasks not sharing the same cpuset
On Wed, 10 Feb 2010 08:32:08 -0800 (PST)
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 <>

Reviewed-by: KAMEZAWA Hiroyuki <>

 \ /
  Last update: 2010-02-12 00:59    [W:0.190 / U:4.540 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site