On Thu, 10 Mar 2011, KAMEZAWA Hiroyuki wrote: > On Wed, 9 Mar 2011 13:27:50 -0800 (PST) > David Rientjes <rientjes@xxxxxxxxxx> wrote: > > > When a memcg is oom and current has already received a SIGKILL, then give > > it access to memory reserves with a higher scheduling priority so that it > > may quickly exit and free its memory. > > > > This is identical to the global oom killer and is done even before > > checking for panic_on_oom: a pending SIGKILL here while panic_on_oom is > > selected is guaranteed to have come from userspace; the thread only needs > > access to memory reserves to exit and thus we don't unnecessarily panic > > the machine until the kernel has no last resort to free memory. > > > > Signed-off-by: David Rientjes <rientjes@xxxxxxxxxx> > > Acked-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@xxxxxxxxxxxxxx> > > Thank you. > I'm hoping this can make 2.6.39 so that userspace can kill a thread in a memcg when it is oom and the oom killer is disabled via memory.oom_control and it will still get access to memory reserves if needed while trying to exit. -- 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 internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>