From: Andi Kleen <ak@suse.de>
To: Steve Lord <lord@xfs.org>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org, kenneth.w.chen@intel.com
Subject: Re: Limit hash table size
Date: Fri, 6 Feb 2004 05:39:27 +0100 [thread overview]
Message-ID: <20040206053927.37709591.ak@suse.de> (raw)
In-Reply-To: <4021C152.3080501@xfs.org>
On Wed, 04 Feb 2004 22:06:42 -0600
Steve Lord <lord@xfs.org> wrote:
> It does look like 2.6 does better, but I don't have quite the
> amount of memory on my laptop....
I see the problem on a 8GB x86-64 box with 2.6.2-rc1.
After a find / I have:
Active / Total Objects (% used) : 1794827 / 1804510 (99.5%)
Active / Total Slabs (% used) : 125647 / 125647 (100.0%)
Active / Total Caches (% used) : 71 / 112 (63.4%)
Active / Total Size (% used) : 685008.27K / 686856.36K (99.7%)
Minimum / Average / Maximum Object : 0.02K / 0.38K / 128.00K
OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
708600 708559 99% 0.25K 47240 15 188960K dentry_cache
624734 624128 99% 0.69K 56794 11 454352K reiser_inode_cache
254200 253514 99% 0.09K 6355 40 25420K buffer_head
109327 109253 99% 0.06K 1853 59 7412K size-64
Now I allocate 6GB of RAM. After that:
Active / Total Objects (% used) : 741266 / 1092573 (67.8%)
Active / Total Slabs (% used) : 78291 / 78291 (100.0%)
Active / Total Caches (% used) : 71 / 112 (63.4%)
Active / Total Size (% used) : 339837.24K / 455189.93K (74.7%)
Minimum / Average / Maximum Object : 0.02K / 0.42K / 128.00K
OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME
464497 381126 82% 0.69K 42227 11 337816K reiser_inode_cache
391545 192481 49% 0.25K 26103 15 104412K dentry_cache
135840 95304 70% 0.09K 3396 40 13584K buffer_head
1GB of dentry cache seems to be quite excessive.
-Andi
next prev parent reply other threads:[~2004-02-06 4:46 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <B05667366EE6204181EABE9C1B1C0EB5802441@scsmsx401.sc.intel.com.suse.lists.linux.kernel>
[not found] ` <20040205155813.726041bd.akpm@osdl.org.suse.lists.linux.kernel>
2004-02-06 1:54 ` Limit hash table size Andi Kleen
2004-02-05 2:38 ` Steve Lord
2004-02-06 3:12 ` Andrew Morton
2004-02-05 4:06 ` Steve Lord
2004-02-06 4:39 ` Andi Kleen [this message]
2004-02-06 4:59 ` Andrew Morton
2004-02-06 5:34 ` Maneesh Soni
2004-02-06 3:19 ` Andi Kleen
2004-02-06 3:23 ` Nick Piggin
2004-02-06 3:34 ` Andrew Morton
2004-02-06 3:38 ` Nick Piggin
2004-02-18 12:41 ` Pavel Machek
2004-02-06 3:09 ` Andrew Morton
2004-02-06 3:18 ` Andi Kleen
2004-02-06 3:30 ` Andrew Morton
2004-02-06 4:45 ` Martin J. Bligh
2004-02-06 6:22 ` Matt Mackall
2004-02-06 20:20 ` Taneli Vähäkangas
2004-02-06 20:27 ` Andrew Morton
2004-02-06 21:46 ` Taneli Vähäkangas
2004-02-18 0:45 Chen, Kenneth W
-- strict thread matches above, loose matches on Subject: below --
2004-02-18 0:16 Chen, Kenneth W
2004-02-17 22:24 Chen, Kenneth W
2004-02-17 23:24 ` Andrew Morton
2004-02-06 6:32 Manfred Spraul
2004-02-06 0:10 Chen, Kenneth W
2004-02-06 0:23 ` Andrew Morton
2004-02-09 23:12 ` Jes Sorensen
2004-01-14 22:31 Chen, Kenneth W
2004-01-18 14:25 ` Anton Blanchard
2004-01-14 22:29 Chen, Kenneth W
2004-01-12 16:50 Manfred Spraul
2004-01-09 19:05 Chen, Kenneth W
2004-01-12 13:32 ` Anton Blanchard
2004-01-08 23:12 Chen, Kenneth W
2004-01-09 9:25 ` Andrew Morton
2004-01-09 14:25 ` Anton Blanchard
2004-02-05 23:58 ` Andrew Morton
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=20040206053927.37709591.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lord@xfs.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