Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 4 Aug 2002 14:28:03 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 4 Aug 2002 14:28:03 -0400 Received: from thebsh.namesys.com ([212.16.7.65]:42246 "HELO thebsh.namesys.com") by vger.kernel.org with SMTP id ; Sun, 4 Aug 2002 14:28:02 -0400 Message-ID: <3D4D72EB.7000809@namesys.com> Date: Sun, 04 Aug 2002 22:31:07 +0400 From: Hans Reiser User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020529 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Rik van Riel CC: Andreas Gruenbacher , Linus Torvalds , Alan Cox , Marcelo Tosatti , lkml Subject: Re: [PATCH] Caches that shrink automatically References: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1135 Lines: 37 Rik van Riel wrote: >On Sun, 4 Aug 2002, Andreas Gruenbacher wrote: > > >>On Sunday 04 August 2002 13:30, Hans Reiser wrote: >> >> >>>How do you ensure that caches have their (internal) aging hands pushed >>>at a speed that is proportional to their memory usage, or is your design >>>susceptible to all the usual complaints the unified memory manager crowd >>>has about separate caches? >>> >>> >>That's a policy/optimization issue; it's not even desirable to shrink the >>caches with priorities proportional to their size---they would all tend to >>become equally large. >> >> > >Nope, the idea is to push all caches according to size, but >often-used caches should shrink less than caches that are >hardly ever used. > Do you let the subcache decide how to move the aging hand and track it? Have I convinced you of that one yet? Or is it still page based? -- Hans - 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/