linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Cliff Wickman <cpw@sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: [PATCH 1/1] shrink dentry cache before inode cache
Date: Wed, 1 Mar 2006 14:12:20 -0800	[thread overview]
Message-ID: <20060301141220.7728795f.akpm@osdl.org> (raw)
In-Reply-To: <20060301170712.GA18066@sgi.com>

Cliff Wickman <cpw@sgi.com> wrote:
>
> The shrink_slab() function must often be called twice to get significant
> slab cache reduction.
> 
> shrink_slab() walks the shrinker_list to call functions that can
> release kernel slab memory.
> 
> The shrinker_list is walked head to tail and, as it is now, comes across the
> inode cache shrinker first.  This releases inodes found on the inode_unused 
> list.  Afterwards the dentry cache shrinker moves many freeable inodes to 
> the list.  But those inodes are not freed until a second invocation of 
> shrink_slab().
> 
> The dentry cache shrinker (shrink_dcache_memory()) should run before 
> the inode cache shrinker (shrink_icache_memory()).
> 
> This can be accomplished by queuing the dentry cache shrinker earlier -
> simply calling inode_init() before dcache_init().

Is logical, although the implementation is fragile.  This came up a year or
so ago and we decided it wouldn't make any difference - iirc because slab
shrinking tends to occur in little bites across the whole list.

Do you have any measurements or instrumentation which show improvement?

--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2006-03-01 22:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-01 17:07 Cliff Wickman
2006-03-01 22:12 ` Andrew Morton [this message]

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=20060301141220.7728795f.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=cpw@sgi.com \
    --cc=linux-mm@kvack.org \
    /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