Re: Misleading OOM messages
From: Balbir Singh
Date: Sat May 16 2009 - 23:43:23 EST
* Christoph Lameter <cl@xxxxxxxxxxxxxxxxxxxx> [2009-05-15 15:26:43]:
> On Fri, 15 May 2009, Dave Hansen wrote:
>
> > 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.
>
> But that is a resource control isssue. Should also not say out of memory
> but state that the cgroup memory limit was reached.
>
But we are out of memory for the cgroup under consideration.
--
Balbir
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/