Messages in this thread | | | Date | Tue, 23 Feb 2010 12:01:29 +0530 | From | Balbir Singh <> | Subject | Re: [patch -mm 3/9 v2] oom: select task from tasklist for mempolicy ooms |
| |
* David Rientjes <rientjes@google.com> [2010-02-15 14:20:06]:
> 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>
Seems reasonable, but I think it will require lots of testing. -- Three Cheers, Balbir
| |