From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 12 Jun 2001 17:04:09 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 12 Jun 2001 17:04:00 -0400 Received: from pD903C76E.dip.t-dialin.net ([217.3.199.110]:37839 "HELO enterprise.lokalnetz") by vger.kernel.org with SMTP id ; Tue, 12 Jun 2001 17:03:53 -0400 Date: Tue, 12 Jun 2001 23:02:21 +0200 To: Rik van Riel Cc: "Alok K. Dhir" , linux-kernel@vger.kernel.org Subject: Re: 2.4.6-pre2 VM Message-ID: <20010612230220.A30693@mobile> In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.18i From: Erik Tews Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 12, 2001 at 01:17:05AM -0300, Rik van Riel wrote: > On Mon, 11 Jun 2001, Alok K. Dhir wrote: > > > Just wondering - has anyone who was having issues with the VM > > subsystem in 2.4.5 and a few versions below tried v2.4.6-pre2? > > Is the problem reduced and/or resolved? > > The answer is both yes and no, depending on which VM problem > you're talking about. ;) What is about the problem that 2.4.x is swapping out too much? Are there currently any patches for testing? Or are there some values in proc which can change this bad vm-behaviour?