public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dipankar Sarma <dipankar@in.ibm.com>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: ext2-devel <ext2-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: inode cache, dentry cache, buffer heads usage
Date: Thu, 10 Mar 2005 03:23:49 +0530	[thread overview]
Message-ID: <20050309215349.GD4663@in.ibm.com> (raw)
In-Reply-To: <1110403763.24286.213.camel@dyn318077bld.beaverton.ibm.com>

On Wed, Mar 09, 2005 at 01:29:23PM -0800, Badari Pulavarty wrote:
> On Wed, 2005-03-09 at 13:27, Dipankar Sarma wrote:
> > On Wed, Mar 09, 2005 at 10:55:58AM -0800, Badari Pulavarty wrote:
> > > Hi,
> > > 
> > > We have a 8-way P-III, 16GB RAM running 2.6.8-1. We use this as
> > > our server to keep source code, cscopes and do the builds.
> > > This machine seems to slow down over the time. One thing we
> > > keep noticing is it keeps running out of lowmem. Most of 
> > > the lowmem is used for ext3 inode cache + dentry cache +
> > > bufferheads + Buffers. So we did 2:2 split - but it improved
> > > thing, but again run into same issues.
> > > 
> > > So, why is these slab cache are not getting purged/shrinked even
> > > under memory pressure ? (I have seen lowmem as low as 6MB). What
> > > can I do to keep the machine healthy ?
> > 
> > How does /proc/sys/fs/dentry-state look when you run low on lowmem ?
> 
> 
> 
> badari@kernel:~$ cat /proc/sys/fs/dentry-state
> 1434093 1348947 45      0       0       0
> badari@kernel:~$ grep dentry /proc/slabinfo
> dentry_cache      1434094 1857519    144   27    1 : tunables  120  
> 60    8 : slabdata  68797  68797      0

Hmm.. so we are not shrinking dcache despite a large number of
unsed dentries. That is where we need to look. Will dig a bit
tomorrow.

Thanks
Dipankar

  reply	other threads:[~2005-03-09 21:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-09 18:55 inode cache, dentry cache, buffer heads usage Badari Pulavarty
2005-03-09 21:27 ` Dipankar Sarma
2005-03-09 21:29   ` Badari Pulavarty
2005-03-09 21:53     ` Dipankar Sarma [this message]
2005-03-09 21:57       ` [Ext2-devel] " Sonny Rao
2005-03-11  1:47 ` Andrew Morton
2005-03-14 21:28   ` Badari Pulavarty
2005-03-14 22:11     ` Andrew Morton
2005-03-14 22:13       ` [Ext2-devel] " Badari Pulavarty
2005-03-14 22:41         ` Andrew Morton
2005-03-15 16:17           ` Badari Pulavarty

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=20050309215349.GD4663@in.ibm.com \
    --to=dipankar@in.ibm.com \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbadari@us.ibm.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