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:13:17 -0700 [thread overview]
Message-ID: <3D755E2D.7A6D55C6@zip.com.au> (raw)
In-Reply-To: <20020904004028.GS888@holomorphy.com>
William Lee Irwin III wrote:
>
> On Mon, Sep 02, 2002 at 09:16:44PM -0700, Andrew Morton wrote:
> > http://www.zip.com.au/~akpm/linux/patches/2.5/2.5.33/2.5.33-mm1/
> > Seven new patches - mostly just code cleanups.
> > +slablru-speedup.patch
> > A patch to improve slablru cpu efficiency. Ed is
> > redoing this.
>
> count_list() appears to be the largest consumer of cpu after this is
> done, or so say the profiles after running updatedb by hand on
> 2.5.33-mm1 on a 900MHz P-III T21 Thinkpad with 256MB of RAM.
That's my /proc/meminfo:buffermem counter-upper. I said it would suck ;)
Probably count_list(&inode_unused) can just be nuked. I don't think blockdev
inodes ever go onto inode_unused.
> 4608 __rdtsc_delay 164.5714
> 2627 __generic_copy_to_user 36.4861
> 2401 count_list 42.8750
> 1415 find_inode_fast 29.4792
> 1325 do_anonymous_page 3.3801
>
> It also looks like there's either a bit of internal fragmentation or a
> missing kmem_cache_reap() somewhere:
>
> ext3_inode_cache: 20001KB 51317KB 38.97
> dentry_cache: 4734KB 18551KB 25.52
> radix_tree_node: 1811KB 1923KB 94.20
> buffer_head: 1132KB 1378KB 82.12
That's really outside the control of slablru. It's determined
by the cache-specific LRU algorithms, and the allocation order.
You'll need to look at the second-last and third-last columns in
/proc/slabinfo (boy I wish that thing had a heading line, or a nice
program to interpret it):
ext3_inode_cache 959 2430 448 264 270 1
That's 264 pages in use, 270 total. If there's a persistent gap between
these then there is a problem - could well be that slablru is not locating
the pages which were liberated by the pruning sufficiently quickly.
Calling kmem_cache_reap() after running the pruners will fix that up.
--
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:13 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 ` Andrew Morton [this message]
2002-09-04 1:15 ` 2.5.33-mm1 William Lee Irwin III
2002-09-04 1:37 ` 2.5.33-mm1 Andrew Morton
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=3D755E2D.7A6D55C6@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