From: Nikita Danilov <Nikita@Namesys.COM>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: Ed Tomlinson <tomlins@cam.org>, linux-mm@kvack.org
Subject: Re: [RFC][PATCH] dcache and rmap
Date: Mon, 13 May 2002 15:07:19 +0400 [thread overview]
Message-ID: <15583.40551.778094.604938@laputa.namesys.com> (raw)
In-Reply-To: <20020507125712.GM15756@holomorphy.com>
William Lee Irwin III writes:
> At some point in the past, I wrote:
> >> In short, I don't think you went far enough. How do you feel about
> >> GFP_SPECULATIVE (a.k.a. GFP_DONT_TRY_TOO_HARD), cache priorities and
> >> cache shrinking drivers?
>
> On Tue, May 07, 2002 at 07:41:52AM -0400, Ed Tomlinson wrote:
> > Think I will sprinkle slab.c with a printk or two to see if we detect when
> > it's allocations are eating other caches. If this works we should be able to
> > let the vm know when to shrink the slab cache and to let it know which
> > caches need shrinking (ie shrink_caches becomes a 'driver' to shrink the
> > dcache/icache family. kmem_cache_reap being the generic 'driver')
> > Thanks for the feedback and interesting idea,
>
> Well, the trick is kmem_cache_reap() doesn't know how to prune
> references to things within the cache like prune_dcache() does. It is
> in essence its own cache in front of another cache for allocations. I'm
> not sure making kmem_cache_reap() trigger reaping of the caches it's
> parked in front of is a great idea. It seems that it would go the other
> direction: reaping a cache parked in front of a slab would want to call
> kmem_cache_reap() sometime afterward (so the memory is actually
> reclaimed instead of sitting in the slab cache). IIRC the VM actually
> does this at some point after calling the assorted cache shrink functions.
> kmem_cache_reap() may well be needed in contexts where the caches are
> doing fine jobs of keeping their space under control or shrinking
> themselves just fine, without intervention from outside callers.
I remember Linus once mentioned an idea that slab pages should have
->writepage() that triggers shrink of the front-end cache.
Along this way, VM would just manage one big cache---physical memory.
>
>
> Cheers,
> Bill
Nikita.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next prev parent reply other threads:[~2002-05-13 11:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-06 1:17 Ed Tomlinson
2002-05-06 2:55 ` Martin J. Bligh
2002-05-06 7:54 ` Ed Tomlinson
2002-05-06 14:40 ` Martin J. Bligh
2002-05-06 15:12 ` Ed Tomlinson
2002-05-07 1:44 ` William Lee Irwin III
2002-05-07 11:41 ` Ed Tomlinson
2002-05-07 12:57 ` William Lee Irwin III
2002-05-07 14:10 ` Christoph Hellwig
2002-05-07 14:48 ` William Lee Irwin III
2002-05-13 11:07 ` Nikita Danilov [this message]
2002-05-13 11:50 ` Ed Tomlinson
2002-05-13 21:23 ` Andrew Morton
2002-05-07 1:01 Lever, Charles
2002-05-07 2:05 ` Martin J. Bligh
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=15583.40551.778094.604938@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=linux-mm@kvack.org \
--cc=tomlins@cam.org \
--cc=wli@holomorphy.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