| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sun, 8 May 2011 16:21:20 +0800 From: Hillf Danton <dhillf@...il.com> To: David Rientjes <rientjes@...gle.com> Cc: linux-mm@...ck.org, LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>, Andrew Morton <akpm@...ux-foundation.org>, Yong Zhang <yong.zhang0@...il.com> Subject: Re: [Question] how to detect mm leaker and kill? On Sat, May 7, 2011 at 6:48 AM, David Rientjes <rientjes@...gle.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 from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists