From: Andrew Morton <akpm@zip.com.au>
To: William Lee Irwin III <wli@holomorphy.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: 2.5.33-mm1
Date: Tue, 03 Sep 2002 18:37:04 -0700 [thread overview]
Message-ID: <3D7563C0.99EE8843@zip.com.au> (raw)
In-Reply-To: <20020904011503.GT888@holomorphy.com>
William Lee Irwin III wrote:
>
> ...
> > Calling kmem_cache_reap() after running the pruners will fix that up.
>
> # grep ext3_inode_cache /proc/slabinfo
> ext3_inode_cache 18917 87012 448 7686 9668 1
> ...
> ext3_inode_cache: 8098KB 38052KB 21.28
>
> Looks like a persistent gap from here.
OK, thanks. We need to reap those pages up-front rather than waiting
for them to come to the tail of the LRU.
What on earth is going on with kmem_cache_reap? Am I missing
something, or is that thing 700% overdesigned? Why not just
free the darn pages in kmem_cache_free_one()? Maybe hang onto
a few pages for cache warmth, but heck.
--
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-09-04 1:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 4:16 2.5.33-mm1 Andrew Morton
2002-09-04 0:40 ` 2.5.33-mm1 William Lee Irwin III
2002-09-04 0:53 ` 2.5.33-mm1 Rik van Riel
2002-09-04 1:13 ` 2.5.33-mm1 Andrew Morton
2002-09-04 1:15 ` 2.5.33-mm1 William Lee Irwin III
2002-09-04 1:37 ` Andrew Morton [this message]
2002-09-04 2:55 ` 2.5.33-mm1 Ed Tomlinson
2002-09-04 2:54 ` 2.5.33-mm1 William Lee Irwin III
2002-09-04 2:51 2.5.33-mm1 Ed Tomlinson
2002-09-04 3:33 ` 2.5.33-mm1 Andrew Morton
2002-09-04 19:25 ` 2.5.33-mm1 Stephen C. Tweedie
2002-09-04 20:18 ` 2.5.33-mm1 Andrew Morton
2002-09-04 9:06 2.5.33-mm2 Andrew Morton
2002-09-04 17:16 ` 2.5.33-mm1 Paul Larson
2002-09-04 18:02 ` 2.5.33-mm1 Andrew Morton
2002-09-04 20:07 ` 2.5.33-mm1 Paul Larson
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=3D7563C0.99EE8843@zip.com.au \
--to=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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