From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <393EBEB5.AEEFF501@reiser.to> Date: Wed, 07 Jun 2000 14:29:25 -0700 From: Hans Reiser MIME-Version: 1.0 Subject: Re: journaling & VM (was: Re: reiserfs being part of the kernel: it'snot just the code) References: <20000607144102.F30951@redhat.com> <20000607154620.O30951@redhat.com> <393EAD84.A4BB6BD9@reiser.to> <20000607215436.F30951@redhat.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: "Stephen C. Tweedie" Cc: "Quintela Carreira Juan J." , Rik van Riel , bert hubert , linux-kernel@vger.rutgers.edu, Chris Mason , linux-mm@kvack.org, Alexander Zarochentcev List-ID: "Stephen C. Tweedie" wrote: > > Hi, > > On Wed, Jun 07, 2000 at 01:16:04PM -0700, Hans Reiser wrote: > > > "Quintela Carreira Juan J." wrote: > > > If you need pages in the LRU cache only for getting notifications, > > > then change the system to send notifications each time that we are > > > short of memory. > > > > I think the right thing is for the filesystems to use the LRU code as templates > > from which they may vary or not from in implementing their subcaches with their > > own lists. I say this for intuitive not concrete reasons. > > Every time we have tried to keep the caches completely separate, we > have ended up losing the ability to balance the various caches against > each other. The major advantage of a common set of LRU lists is that > it gives us a basis for a balanced VM. > > Cheers, > Stephen If I understand Juan correctly, they fixed this issue. Aging 1/64th of the cache for every cache evenly at every round of trying to free pages should be an excellent fix. It should do just fine at the task of handling a system with both ext3 and reiserfs running. Was this Juan's code that did this? If so, kudos to him. Hans -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux.eu.org/Linux-MM/