public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans Reiser <reiser@namesys.com>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: 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:29:24 +0400	[thread overview]
Message-ID: <3D4D7284.7050507@namesys.com> (raw)
In-Reply-To: 200208041511.27990.agruen@suse.de

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.
>
That is not what I said, I said move the aging hand at a speed 
proportional to size, what affect the aging has depends on the usage of 
the objects in the cache.

>
>The patch shrinks all the caches equally often, with the same priorities. 
>
This is wrong, because frequently used objects should not be shrunk out 
of their caches.

>The 
>caches can then decide themselves how they will react, depending on their 
>cache size and entry size, replacement strategy, taking care of page entry 
>clustering or not, etc.
>
How can they decide this without a pressure signal from the master 
memory manager that is proportional to their size?  Or is the idea that 
they figure out their own size?  I suppose that is equivalent....

>
>The icache, dcache, and dqcache are shrunk using the same strategy (except the 
>priority is a constant for some of the caches, which could be coded in the 
>shrink function as well). 
>
What does priority

>This scheme has worked out pretty well so far, 
>right?
>
 Our cache management has deep algorithm flaws which result in things 
like one active dcache entry keeping an entire page of unused dcache 
entries from expiring from the cache.  Did you see Joshua MacDonald's 
post on that topic?

>
>For Extended Attributes we are currently using a very simple cache with LRU 
>entry replacement, and small entries. The cache doesn't grow very big, 
>either.
>
You don't support eas that are larger than a page?  Is it LRU on each 
ea, or is it LRU on the page containing the ea?

>
>Regards,
>Andreas.
>
>------------------------------------------------------------------
> Andreas Gruenbacher                                SuSE Linux AG
> mailto:agruen@suse.de                     Deutschherrnstr. 15-19
> http://www.suse.de/                   D-90429 Nuernberg, Germany
>
>
>
>  
>


-- 
Hans




  parent reply	other threads:[~2002-08-04 18:26 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
2002-08-05  7:44                   ` Joshua MacDonald
2002-08-04 21:42               ` Eric W. Biederman
2002-08-04 18:29     ` Hans Reiser [this message]
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=3D4D7284.7050507@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=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