Date: Fri, 29 Sep 2006 17:34:11 -0400
From: Dave Jones <davej@redhat.com>
To: Larry Woodman <lwoodman@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: oom kill oddness.
Message-ID: <20060929213411.GG22014@redhat.com>
Mail-Followup-To: Dave Jones <davej@redhat.com>,
	Larry Woodman <lwoodman@redhat.com>, linux-kernel@vger.kernel.org
References: <451D7C02.2090907@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <451D7C02.2090907@redhat.com>
User-Agent: Mutt/1.4.2.2i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1007
Lines: 27

On Fri, Sep 29, 2006 at 04:03:14PM -0400, Larry Woodman wrote:
 
 > Dave, this has been a problem since the out_of_memory() function was 
 > changed
 > between 2.6.10 and 2.6.11.  Before this change out_of_memory() required 
 > multiple
 > calls within 5 seconds before actually OOM killed a process.  After the 
 > change(in 2.6.11)
 > a single call to out_of_memory() results in OOM killing a process.  The 
 > following patch
 > allows the 2.6.18 system to run under much more memory pressure before 
 > it OOM kills.

Some of these tests do seem to be readded in Linus' current tree.

[PATCH] oom: don't kill current when another OOM in progress

went in earlier today for eg.
I'm curious why these checks were ever removed in the first place though.

	Dave

-
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/