From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758074AbZEQDnT (ORCPT ); Sat, 16 May 2009 23:43:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755123AbZEQDml (ORCPT ); Sat, 16 May 2009 23:42:41 -0400 Received: from e4.ny.us.ibm.com ([32.97.182.144]:39909 "EHLO e4.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754209AbZEQDmj (ORCPT ); Sat, 16 May 2009 23:42:39 -0400 Date: Sat, 16 May 2009 02:01:22 +0530 From: Balbir Singh To: Christoph Lameter Cc: Dave Hansen , Pavel Machek , David Rientjes , Andrew Morton , Greg Kroah-Hartman , Nick Piggin , Mel Gorman , Peter Ziljstra , San Mehat , Arve Hj?nnev?g , linux-kernel@vger.kernel.org Subject: Re: Misleading OOM messages Message-ID: <20090515203122.GM4451@balbir.in.ibm.com> Reply-To: balbir@linux.vnet.ibm.com References: <20090514092909.GG1365@ucw.cz> <1242333519.15391.210.camel@nimitz> <1242335120.15391.242.camel@nimitz> <20090514213403.GB14741@elf.ucw.cz> <1242411307.28257.25.camel@nimitz> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Christoph Lameter [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