Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267730AbUJHDQY (ORCPT ); Thu, 7 Oct 2004 23:16:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267648AbUJHDPd (ORCPT ); Thu, 7 Oct 2004 23:15:33 -0400 Received: from parcelfarce.linux.theplanet.co.uk ([195.92.249.252]:6871 "EHLO www.linux.org.uk") by vger.kernel.org with ESMTP id S267561AbUJHDIW (ORCPT ); Thu, 7 Oct 2004 23:08:22 -0400 Date: Thu, 7 Oct 2004 22:05:39 -0300 From: Marcelo Tosatti To: Marc-Christian Petersen Cc: "Gabor Z. Papp" , Michael Buesch , linux kernel mailing list Subject: Re: [2.4] 0-order allocation failed Message-ID: <20041008010539.GB16968@logos.cnet> References: <200410071318.21091.mbuesch@freenet.de> <20041007153929.GB14614@logos.cnet> <200410072054.17097@WOLK> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200410072054.17097@WOLK> User-Agent: Mutt/1.5.5.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1731 Lines: 44 On Thu, Oct 07, 2004 at 08:54:16PM +0200, Marc-Christian Petersen wrote: > On Thursday 07 October 2004 20:28, Gabor Z. Papp wrote: > > Hi all, > > > | > > Can you check how much swap space is there available when > > | > > the OOM killer trigger? I bet this is the case. > > | > The machine doesn't have swap. > > | Well then you're probably facing true OOM. > > | Add some swap. > > > There is really no way to run 2.4 without swap? > > I have the same problem with nfsroot and ramdisk based setups after > > 1-2 weeks uptime. > > stop whining about braindead 2.4 mainline vm. Apply the attached patch and be > happy :p As I told you in private, I can't see how badly this patch could affect performance. But then, as you answered, with all anonymous pages added to LRU you see much better behavior (tons less swapping) on several workloads. That must be due to refill_inactive()/shrink_cache() balancing. The same patch also fixes kswapd excessive CPU consumption on huge memory box. Its easy enough to be applied because behaviour is unchanged by default (you need to change a sysctl value for that). I would like to understand why does it cause so much improved behaviour though. > Marcelo: Is there something wrong with my VM documentation update patches for > 2.4? Or do you not care and think: "Hello my friend, let's stick with 2.2 VM > documentation even if almost all of the documentation is not longer valid" As I said to you in private, please resend. Thanks! - 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/