From: Hans Reiser <reiser@namesys.com>
To: Rik van Riel <riel@conectiva.com.br>
Cc: Andreas Gruenbacher <agruen@suse.de>,
Linus Torvalds <torvalds@transmeta.com>,
Alan Cox <alan@redhat.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Caches that shrink automatically
Date: Sun, 04 Aug 2002 22:31:07 +0400 [thread overview]
Message-ID: <3D4D72EB.7000809@namesys.com> (raw)
In-Reply-To: Pine.LNX.4.44L.0208041055160.23404-100000@imladris.surriel.com
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
next prev parent reply other threads:[~2002-08-04 18:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-04 11:08 [PATCH] Caches that shrink automatically Andreas Gruenbacher
2002-08-04 11:30 ` Hans Reiser
2002-08-04 13:11 ` Andreas Gruenbacher
2002-08-04 13:56 ` Rik van Riel
2002-08-04 18:31 ` Hans Reiser [this message]
2002-08-04 18:44 ` Rik van Riel
2002-08-04 18:50 ` Linus Torvalds
2002-08-04 18:59 ` Rik van Riel
2002-08-04 19:05 ` Linus Torvalds
2002-08-04 19:17 ` Hans Reiser
2002-08-05 7:44 ` Joshua MacDonald
2002-08-04 21:42 ` Eric W. Biederman
2002-08-04 18:29 ` Hans Reiser
2002-08-04 18:43 ` Linus Torvalds
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D4D72EB.7000809@namesys.com \
--to=reiser@namesys.com \
--cc=agruen@suse.de \
--cc=alan@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=riel@conectiva.com.br \
--cc=torvalds@transmeta.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox