[cgl_discussion] Re: About Replaceable OOM Killer
Cress, Andrew R
andrew.r.cress at intel.com
Mon Mar 15 05:45:20 PST 2004
Right, once it is really OOM, you are SOL :-) Really the only thing you can do at this point in the kernel is to not allocate any more memory, and functions that require more memory just don't work, and the recovery is to reboot..
IMO, the best answer is to detect a nearly-OOM, or trending-toward-OOM condition before it gets so bad.
This would allow userland actions, but would require more customization to tune the detection criteria, which would also imply a userland implementation of the monitoring. We've found that PCP works pretty well for this type of thing.
See http://oss.sgi.com/projects/pcp/ and http://pcp4cgl.sourceforge.net/. We did some work with this for CGL 1.0.
From: cgl_discussion-bounces at lists.osdl.org [mailto:cgl_discussion-bounces at lists.osdl.org] On Behalf Of Pavel Machek
Sent: Monday, March 08, 2004 6:02 AM
To: Yury V. Umanets
Cc: Guo, Min; Tvrtko A. Uršulin; linux-kernel at vger.kernel.org; cgl_discussion at lists.osdl.org
Subject: [cgl_discussion] Re: About Replaceable OOM Killer
> > Though it hasn't been updated for a while because nobody cares...
> IMHO problem with OOM killer is that it always will do wrong choice. So,
> it should be either plugin based or allow to configure it and this
> means, that it will become more complex and buggy. Does not it mean,
> that OOM killer should be moved to user space?
> How about to export OOM event to user space? It might be done in manner
> like hotplug script is used.
When you are OOM, you really can't exec userland script...
64 bytes from 18.104.22.168: icmp_seq=28 ttl=51 time=448769.1 ms
cgl_discussion mailing list
cgl_discussion at lists.osdl.org
More information about the cgl_discussion