kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: bill4carson@gmail.com (bill4carson)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Query about Enhanced Out-Of-Memory handling
Date: Mon, 05 Dec 2011 11:24:37 +0800	[thread overview]
Message-ID: <4EDC3975.8090300@gmail.com> (raw)

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

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

             reply	other threads:[~2011-12-05  3:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-05  3:24 bill4carson [this message]
2011-12-11  6:38 ` Query about Enhanced Out-Of-Memory handling Peter Teoh
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=4EDC3975.8090300@gmail.com \
    --to=bill4carson@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).