Date: Wed, 23 Mar 2005 15:30:06 -0800
From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Andries Brouwer <aebr@win.tue.nl>, Andrew Morton <akpm@osdl.org>
cc: cmm@us.ibm.com, andrea@suse.de, linux-kernel@vger.kernel.org,
       ext2-devel@lists.sourceforge.net
Subject: Re: OOM problems on 2.6.12-rc1 with many fsx tests
Message-ID: <25760000.1111620606@flay>
In-Reply-To: <20050323232656.GA5704@pclin040.win.tue.nl>
References: <20050315204413.GF20253@csail.mit.edu> <20050316003134.GY7699@opteron.random> <20050316040435.39533675.akpm@osdl.org> <20050316183701.GB21597@opteron.random> <1111607584.5786.55.camel@localhost.localdomain> <20050323144953.288a5baf.akpm@osdl.org> <17250000.1111619602@flay> <20050323152055.6fc8c198.akpm@osdl.org> <20050323232656.GA5704@pclin040.win.tue.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 769
Lines: 25

>> Nothing beats poking around in a dead machine's guts with kgdb though.
> 
> Everyone his taste.
> 
> But I was surprised by
> 
>> SwapTotal:     1052216 kB
>> SwapFree:      1045984 kB
> 
> Strange that processes are killed while lots of swap is available.

I don't think we're that smart about it. If we're really low on mem, it
seems we invoke the OOM killer whether processes are causing the problem
or not. 

OTOH, if we can't free the kernel mem, we don't have much choice, but 
it's not really helping much ;-)

M.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/