From: htmldeveloper@gmail.com (Peter Teoh)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Query about Enhanced Out-Of-Memory handling
Date: Sun, 11 Dec 2011 14:38:21 +0800 [thread overview]
Message-ID: <CAHnt0GUDrCbBOXgYfDbxCa5voL2GH_b7VJTF4p4hFVYa-wUCfA@mail.gmail.com> (raw)
In-Reply-To: <4EDC3975.8090300@gmail.com>
On Mon, Dec 5, 2011 at 11:24 AM, bill4carson <bill4carson@gmail.com> wrote:
> Hi, all
>
> Since there is a practical needs for user application with the ability
> to sense kernel memory use pressure,
> http://elinux.org/Memory_Management gives some approach on this as below:
>
> OOM notification in cgroups
> mem_notify patches
> Google cgroup OOM handler
> Nokia OOM enhancements
>
OOM by itself is for non-critical server, or hand-held devices where
physical memory is severely constrained. For server running database, or
any high end server, it is disastrous to have it turned on. Judge for
yourself the criticality of your applications and turn it on/off if needs
to:
http://serverfault.com/questions/141988/avoid-linux-out-of-memory-application-teardown
http://www.cyberciti.biz/tips/linux-oom-killer-out-of-memory-and-nfs-server-optimization.html
http://lwn.net/Articles/49531/
http://lwn.net/Articles/317814/
http://lwn.net/Articles/391222/
For the latest development, read this:
https://www.redhat.com/archives/linux-audit/2011-May/msg00000.html
and the Documentation/feature-removal-schedule.txt and
Documentation/cgroups/memory.txt
has some development on OOM as well
>
> AFAIK, it seems none of these have been merged into mainline or updated
> continuously,
> I'm not so familiar with mm system, so may I ask which known approach is
> best to work with mainline kernel now?
>
>
>
> --
> I am a slow learner
> but I will keep trying to fight for my dreams!
>
> --bill
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
--
Regards,
Peter Teoh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20111211/edd87808/attachment.html
next prev parent reply other threads:[~2011-12-11 6:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-05 3:24 Query about Enhanced Out-Of-Memory handling bill4carson
2011-12-11 6:38 ` Peter Teoh [this message]
2011-12-12 1:36 ` bill4carson
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=CAHnt0GUDrCbBOXgYfDbxCa5voL2GH_b7VJTF4p4hFVYa-wUCfA@mail.gmail.com \
--to=htmldeveloper@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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).