Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 20 Nov 2001 04:16:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 20 Nov 2001 04:16:13 -0500 Received: from puce.csi.cam.ac.uk ([131.111.8.40]:10954 "EHLO puce.csi.cam.ac.uk") by vger.kernel.org with ESMTP id ; Tue, 20 Nov 2001 04:16:02 -0500 Content-Type: text/plain; charset=US-ASCII From: James A Sutherland To: ebiederm@xmission.com (Eric W. Biederman) Subject: Re: Swap Date: Tue, 20 Nov 2001 09:16:04 +0000 X-Mailer: KMail [version 1.3.1] Cc: Erik Gustavsson , linux-kernel@vger.kernel.org In-Reply-To: <3BF82443.5D3E2E11@starband.net> 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 Tuesday 20 November 2001 2:47 am, Eric W. Biederman wrote: > James A Sutherland writes: > > 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... > > For that page perhaps. But that is only 4K. That doesn't explain the rest > of it. use-once is per page. True - the ID3 can be in several different places, so that could account for a couple of pages, but mp3 players certainly DON'T read the whole file in before playing... Does the mp3 player in question try to pre-read the pages using one process/thread, before the actual player thread reaches them? How far apart would two accesses need to be to disable read-once? 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/