[lkml]   [2009]   [May]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Misleading OOM messages
* Dave Hansen <> [2009-05-15 11:15:07]:

> On Fri, 2009-05-15 at 13:57 -0400, Christoph Lameter wrote:
> > > If you misconfigured cgroups, you give more memory to them.
> >
> > If you do not have enough memory in a cgroup then your application should
> > slow down (because of page evictions) but the system should not OOM.
> > Are cgroups broken or why are you getting OOMs when using them?
> See mm/oom_kill.c::mem_cgroup_out_of_memory(). A group itself can have
> an OOM done on it. It's not a system-wide oom. We just need to ensure
> that we continue to differentiate the cgroup-specific oom message from
> the general one. Maybe also include some more cgroup info in the debug
> outbut.

A long pending action item is to allow user space to handle cgroup
OOM. A cgroup can OOM, if the tasks in the group is way over their limit
and reclaim fails. I'll look to see if we enhance the output.


 \ /
  Last update: 2009-05-15 20:23    [W:0.204 / U:2.352 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site