From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Christian Leber <christian@leber.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.25 - large inode_cache
Date: Thu, 26 Feb 2004 10:08:23 -0300 (BRT) [thread overview]
Message-ID: <Pine.LNX.4.58L.0402261004310.5003@logos.cnet> (raw)
In-Reply-To: <20040226111912.GB4554@core.home>
On Thu, 26 Feb 2004, Christian Leber wrote:
> On Thu, Feb 26, 2004 at 02:33:14AM +0100, Jakob Oestergaard wrote:
> > Besides, after a few days of running, the machine will use about 100MB
> > of memory for cache, 100MB for buffers, about 100MB for userspace, and
> > the remaining 600-700 MB of memory for inode_cache and dentry_cache.
>
> I have the same problem (it's an dual PIII NFS fileserver with promise sx6000
> raid, 320 GB ext3 filesystem and only 512 MB Ram).
>
> After only 2 days running the bloatmeter output looks like:
> inode_cache: 336585KB 357234KB 94.21
> dentry_cache: 50305KB 56523KB 88.99
> size-32: 1516KB 1695KB 89.46
>
> free output is this:
> total used free shared buffers cached
> Mem: 515980 506464 9516 0 2272 19204
> -/+ buffers/cache: 484988 30992
> Swap: 1951856 7992 1943864
This should be normal behaviour -- the i/d caches grew because of file
system activitity. This memory will be reclaimed in case theres pressure.
Is the behaviour different from previous 2.4 or 2.6 kernels?
next prev parent reply other threads:[~2004-02-26 12:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 1:33 Jakob Oestergaard
2004-02-26 11:19 ` Christian Leber
2004-02-26 13:08 ` Marcelo Tosatti [this message]
2004-02-26 13:03 ` Jakob Oestergaard
2004-02-26 14:23 ` Marcelo Tosatti
2004-02-26 13:53 ` Jakob Oestergaard
2004-02-26 17:43 ` Andreas Dilger
2004-02-26 20:43 ` Marcelo Tosatti
2004-02-27 12:27 ` Jakob Oestergaard
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=Pine.LNX.4.58L.0402261004310.5003@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=christian@leber.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®