From: Hans Reiser <reiser@namesys.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
Andreas Gruenbacher <agruen@suse.de>, Alan Cox <alan@redhat.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
lkml <linux-kernel@vger.kernel.org>,
Joshua MacDonald <jmacd@namesys.com>
Subject: Re: [PATCH] Caches that shrink automatically
Date: Sun, 04 Aug 2002 23:17:03 +0400 [thread overview]
Message-ID: <3D4D7DAF.8080309@namesys.com> (raw)
In-Reply-To: Pine.LNX.4.44.0208041202390.10314-100000@home.transmeta.com
Linus Torvalds wrote:
>On Sun, 4 Aug 2002, Rik van Riel wrote:
>
>
>>>In particular, it is useless for the sub-caches to try to maintain their
>>>own LRU lists and their own accessed bits. But that doesn't mean that
>>>they can _act_ as if they updated their own accessed bits, while really
>>>just telling the page-based thing that that page is active.
>>>
>>>
>>I'm not sure I agree with this. For eg. the dcache you will want
>>to reclaim the less used entries on a page even if there are a few
>>very intensely used entries on that page.
>>
>>
>
>True in theory, but I doubt you will see it very much in practice.
>
>Most of the time when you want to free dentries, it is because you have a
>_ton_ of them.
>
>The fact that some will look cold even if they aren't should not matter
>that much statistically.
>
>Yah, it's a guess. We can test it.
>
> Linus
>
>
>
>
>
Josh tested it. He posted on it. I'll have him find his original post
and repost tomorrow, but summarized in brief, the current dcache
shrinking/management approach was quite inefficient. Each active dcache
entry kept a whole lot of dead ones around.
--
Hans
next prev parent reply other threads:[~2002-08-04 19:14 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
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 [this message]
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=3D4D7DAF.8080309@namesys.com \
--to=reiser@namesys.com \
--cc=agruen@suse.de \
--cc=alan@redhat.com \
--cc=jmacd@namesys.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