On Mon, Dec 5, 2011 at 11:24 AM, bill4carson <[email protected]> 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 > [email protected] > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > -- Regards, Peter Teoh
_______________________________________________ Kernelnewbies mailing list [email protected] http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
