Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 25 Oct 2002 14:38:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 25 Oct 2002 14:38:07 -0400 Received: from packet.digeo.com ([12.110.80.53]:20146 "EHLO packet.digeo.com") by vger.kernel.org with ESMTP id ; Fri, 25 Oct 2002 14:38:07 -0400 Message-ID: <3DB990FE.A1B8956@digeo.com> Date: Fri, 25 Oct 2002 11:44:14 -0700 From: Andrew Morton X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.19-pre4 i686) X-Accept-Language: en MIME-Version: 1.0 To: chrisl@vmware.com CC: Andrea Arcangeli , linux-kernel@vger.kernel.org, chrisl@gnuchina.org, Alan Cox Subject: Re: writepage return value check in vmscan.c References: <20021024082505.GB1471@vmware.com> <3DB7B11B.9E552CFF@digeo.com> <20021024175718.GA1398@vmware.com> <20021024183327.GS3354@dualathlon.random> <20021024191531.GD1398@vmware.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 25 Oct 2002 18:44:14.0823 (UTC) FILETIME=[84496770:01C27C56] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 834 Lines: 25 chrisl@vmware.com wrote: > > bigmm -i 3 -t 2 -c 1024 That's a nice little box killer you have there. With mem=4G, running bigmm -i 5 -t 2 -c 1024: 2.4.19: Ran for a few minutes, got slower and slower and eventually stopped. kupdate had taken 30 seconds CPU and all CPUs were spinning in shrink_cache(). Had to reset. 2.4.20-pre8-ac1: Ran for a minute, froze up for a couple of minutes then recovered and remained comfortable. 2.5.44-mm5: had a few 0.5-second stalls in vmstat output, no other problems. It's probably the list search failure, but I can't say for sure at this time. - 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/