lkml.org 
[lkml]   [2011]   [May]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
DateFri, 6 May 2011 15:48:58 -0700 (PDT)
FromDavid Rientjes <>
SubjectRe: [Question] how to detect mm leaker and kill?
On Fri, 6 May 2011, Hillf Danton wrote:

> Hi
>
> In the scenario that 2GB physical RAM is available, and there is a
> database application that eats 1.4GB RAM without leakage already
> running, another leaker who leaks 4KB an hour is also running, could
> the leaker be detected and killed in mm/oom_kill.c with default
> configure when oom happens?
>

Yes, if you know the database application is going to use 70% of your
system RAM and you wish to discount that from its memory use when being
considered for oom kill, set its /proc/pid/oom_score_adj to -700.

This is only possible on 2.6.36 and later kernels when oom_score_adj was
introduced.

If you'd like to completely disable oom killing, set
/proc/pid/oom_score_adj to -1000.


\
 
 \ /
  Last update: 2011-05-07 00:51    [from the cache]
©2003-2010