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 15:30:56 +0400 [thread overview]
Message-ID: <3D4D1070.1020802@namesys.com> (raw)
In-Reply-To: 200208041308.51638.agruen@suse.de
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?
Hans
Andreas Gruenbacher wrote:
>Hello,
>
>Currently there is no way for modules to define dynamically sized caches that
>shrink upon memory pressure. We need this for implementing Extended Attribute
>caches on ext2, ext3, and ReiserFS. Other caches could also make use of the
>same mechanism (e.g., nfsd's permission cache, dcache, icache, dqache).
>
>I propose this patch, which adds the register_cache() and unregister_cache()
>functions. They allow to register a callback which is invoked on memory
>pressure. This callback shall then try to free some memory; the parameters
>and semantics are similar to the other shrink functions in mm/vmscan.c.
>
>
>Regards,
>Andreas.
>
>------------------------------------------------------------------
> Andreas Gruenbacher SuSE Linux AG
> mailto:agruen@suse.de Deutschherrnstr. 15-19
> http://www.suse.de/ D-90429 Nuernberg, Germany
>
>
>
>
--
Hans
next prev parent reply other threads:[~2002-08-04 11: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 [this message]
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
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=3D4D1070.1020802@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