Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1161242AbWI2A6J (ORCPT ); Thu, 28 Sep 2006 20:58:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1161243AbWI2A6J (ORCPT ); Thu, 28 Sep 2006 20:58:09 -0400 Received: from scrub.xs4all.nl ([194.109.195.176]:7613 "EHLO scrub.xs4all.nl") by vger.kernel.org with ESMTP id S1161242AbWI2A6H (ORCPT ); Thu, 28 Sep 2006 20:58:07 -0400 Date: Fri, 29 Sep 2006 02:57:45 +0200 (CEST) From: Roman Zippel X-X-Sender: roman@scrub.home To: Andrew Morton cc: Dave Jones , Linux Kernel Subject: Re: oom kill oddness. In-Reply-To: <20060928171706.bee0c50b.akpm@osdl.org> Message-ID: References: <20060927205435.GF1319@redhat.com> <20060928171706.bee0c50b.akpm@osdl.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 882 Lines: 27 Hi, On Thu, 28 Sep 2006, Andrew Morton wrote: > Kernel versions please, guys. There have been a lot of oom-killer changes > post-2.6.18. Last I tested this was with 2.6.18. The latest changes to vmscan.c should help... > > If someone wants to play with the problem, the example program below > > triggers the problem relatively easily (booting with only little ram > > helps), it starts a number of readers, which should touch a bit more > > memory than is available and a few writers, which occasionally allocate > > memory. > > > > How much ram, how much swap? I tested it with 32MB and 64MB and plenty of swap. bye, Roman - 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/