From: Hillf Danton <dhillf@gmail.com>
To: linux-mm@kvack.org
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Yong Zhang <yong.zhang0@gmail.com>
Subject: [Question] how to detect mm leaker and kill?
Date: Fri, 6 May 2011 23:04:52 +0800 [thread overview]
Message-ID: <BANLkTi=S_gSvnQimgqrMmq9eWJYDCDRVmA@mail.gmail.com> (raw)
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?
thanks
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>
next reply other threads:[~2011-05-06 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 15:04 Hillf Danton [this message]
2011-05-06 22:48 ` [Question] how to detect mm leaker and kill? David Rientjes
2011-05-08 8:21 ` Hillf Danton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=S_gSvnQimgqrMmq9eWJYDCDRVmA@mail.gmail.com' \
--to=dhillf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=yong.zhang0@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).