Re: [Question] how to detect mm leaker and kill?

[Hillf Danton <dhillf@gmail.com>]

On Sat, May 7, 2011 at 6:48 AM, David Rientjes <rientjes@google.com> wrote:
> 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.
>

Thank you very much, David, for cool answer to my question.

Hillf

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>