| Date | Wed, 10 Feb 2010 17:47:33 -0500 | From | Rik van Riel <> | Subject | Re: [patch 3/7 -mm] oom: select task from tasklist for mempolicy ooms |
| |
On 02/10/2010 11:32 AM, David Rientjes wrote: > The oom killer presently kills current whenever there is no more memory > free or reclaimable on its mempolicy's nodes. There is no guarantee that > current is a memory-hogging task or that killing it will free any > substantial amount of memory, however. > > In such situations, it is better to scan the tasklist for nodes that are > allowed to allocate on current's set of nodes and kill the task with the > highest badness() score. This ensures that the most memory-hogging task, > or the one configured by the user with /proc/pid/oom_adj, is always > selected in such scenarios. > > Signed-off-by: David Rientjes<rientjes@google.com>
Acked-by: Rik van Riel <riel@redhat.com>
-- All rights reversed.
|