From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754579AbZEVGNK (ORCPT ); Fri, 22 May 2009 02:13:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751215AbZEVGNB (ORCPT ); Fri, 22 May 2009 02:13:01 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:57561 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750880AbZEVGNA (ORCPT ); Fri, 22 May 2009 02:13:00 -0400 Date: Tue, 19 May 2009 22:39:45 +0200 From: Pavel Machek To: Christoph Lameter Cc: Dave Hansen , 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: <20090519203944.GD1362@ucw.cz> References: <1242333519.15391.210.camel@nimitz> <1242335120.15391.242.camel@nimitz> <20090514213403.GB14741@elf.ucw.cz> <1242337299.28440.47.camel@nimitz> <20090515130547.GA1976@elf.ucw.cz> <20090515200213.GA1406@ucw.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 On Fri 2009-05-15 17:15:54, Christoph Lameter wrote: > On Fri, 15 May 2009, Pavel Machek wrote: > > > > Nope. If you have too little memory for your app then the kernel pages > > > portions of the app out to disk. Thats is why you have a VM (VIRTUAL > > > machine). The app is not running with physical memory. > > > > Try running your machine with mem=8M, then tell me how virtual memory > > works. > > Well that is of course not enough memory. Ok, so in the end, there are two reasons for OOM: 1) Out of virtual memory. there's simply not enough ram+swap to fit the data. You go OOM. This seems to be common on small machines. 8M is pushing it, but 64M ram + 64M swap + todays gnome would probably do that. And maybe the way to hint people would be printing 'out of _virtual_ memory'. 2) Something goes very wrong with reclaim this seems to be common on very big machines you have experience with. Perhaps 1 and 2 can be told appart by zero swap free in the 1) case? And perhaps you can invent some better message for 2) case? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html