Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 19 Nov 2001 14:12:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 19 Nov 2001 14:12:28 -0500 Received: from mauve.csi.cam.ac.uk ([131.111.8.38]:18145 "EHLO mauve.csi.cam.ac.uk") by vger.kernel.org with ESMTP id ; Mon, 19 Nov 2001 14:12:15 -0500 Content-Type: text/plain; charset=US-ASCII From: James A Sutherland To: ebiederm@xmission.com (Eric W. Biederman), Erik Gustavsson Subject: Re: Swap Date: Mon, 19 Nov 2001 19:12:15 +0000 X-Mailer: KMail [version 1.3.1] Cc: linux-kernel@vger.kernel.org In-Reply-To: <3BF82443.5D3E2E11@starband.net> <1006124602.3890.0.camel@bettan> In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-Id: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Monday 19 November 2001 6:12 pm, Eric W. Biederman wrote: > Erik Gustavsson writes: > > I agree... After a while it always seems that 80% or more of my RAM is > > used for cache and buffers while my open, but not currently used apps > > get pushed onto disk. Then when I decide to switch to that mozilla > > window of emacs session I have to wait for it to be loaded from disk > > again. Also considering the kind of disk activity this box has, the data > > in the cache is mostly the last few hour's MP3's, in other words utterly > > useless as that data will not be used again. I'd rather my apps stayed > > in RAM... > > > > > > Is there a way to limit the size of the cache? > > Reasonable. It looks like the use once heuristics are failing for your > mp3 files. Find out why that is happening and they should push the > rest of your system into swap. Getting clobbered by the mp3 player accessing the ID3 tag? That way, at least part of the file is used twice, so use-ONCE won't matter... James. - 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/