On Wed, 22 Dec 2010 17:48:29 +0900 KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> wrote: > On Wed, 22 Dec 2010 00:48:53 -0800 (PST) > David Rientjes <rientjes@xxxxxxxxxx> wrote: > > > On Wed, 22 Dec 2010, KAMEZAWA Hiroyuki wrote: > > > > > seems to be hard to use. No one can estimate "milisecond" for avoidling > > > OOM-kill. I think this is very bad. Nack to this feature itself. > > > > > > > There's no estimation that is really needed, we simply need to be able to > > stall long enough that we'll eventually kill "something" if userspace > > fails to act. > > > > Why we have to think of usermode failure by mis configuration or user mode bug ? > It's a work of Middleware in usual. For example. oom_check_deadlockd can work as 1. disable oom by memory.oom_disable=1 2. check memory.oom_notify and wait it by poll() 3. At oom, it wakes up. 4. wait for 60 secs. 5. If the cgroup is still in OOM, set oom_disalble=0 This daemon will not use much memory and can run in /roog memory cgroup. Thanks, -Kame -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>