From: Andi Kleen <ak@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: bharata@in.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: dcache leak in 2.6.16-git8
Date: Tue, 28 Mar 2006 09:15:48 +0200 [thread overview]
Message-ID: <200603280915.48793.ak@suse.de> (raw)
In-Reply-To: <20060327190027.24498e3a.akpm@osdl.org>
On Tuesday 28 March 2006 05:00, Andrew Morton wrote:
> Andi Kleen <ak@suse.de> wrote:
> >
> > On Monday 27 March 2006 13:48, Bharata B Rao wrote:
> > > On Mon, Mar 27, 2006 at 07:50:20AM +0200, Andi Kleen wrote:
> > > >
> > > > A 2GB x86-64 desktop system here is currently swapping itself to death after
> > > > a few days uptime.
> > > >
> > > > Some investigation shows this:
> > > >
> > > > inode_cache 1287 1337 568 7 1 : tunables 54 27 8 : slabdata 191 191 0
> > > > dentry_cache 1867436 1867643 208 19 1 : tunables 120 60 8 : slabdata 98297 98297 0
> > > >
> > >
> > > Would it be possible to try out this experimental patch which
> > > gets some stats from the dentry cache ?
> >
> > It should be trivial to reproduce by other people. Biggest workload
> > is kernel compiles and quilt.
> >
> > After a few hours with -git12 it's already at
> >
> > dentry_cache 947013 952014 208 19 1 : tunables 120 60 8 : slabdata 50100 50106 480
> >
> > and starting to go into swap.
> >
> > I can't imagine I'm the only one seeing this?
> >
> > I have a few x86-64 patches applied too, but they don't change anything
> > in this area.
>
> I don't think I can reproduce this on x86 uniproc. (avtab_node_cache
> is a different story - maintainers separately pinged).
This is x86-64 dual core.
>
> I'd expect pretty much everything we have in there now was under test in
> -mm for quite some time - any obvious leaks would have been noticed. I'd
> be suspecting recent changes in perhaps audit or nfs, at a guess. Or
> something weird.
>
> Which filesystems are in use?
ext3, NFS (not much)
-Andi
next prev parent reply other threads:[~2006-03-28 7:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-27 5:50 dcache leak in 2.6.16-git8 Andi Kleen
2006-03-27 11:48 ` Bharata B Rao
2006-03-27 16:22 ` Andi Kleen
2006-03-28 3:00 ` Andrew Morton
2006-03-28 7:15 ` Andi Kleen [this message]
2006-03-29 22:26 ` dcache leak in 2.6.16-git8 II Andi Kleen
2006-03-29 22:50 ` Andrew Morton
2006-03-29 22:53 ` Andi Kleen
2006-03-30 6:41 ` Balbir Singh
2006-03-30 9:50 ` Al Viro
2006-03-30 10:12 ` Al Viro
2006-03-30 10:36 ` Al Viro
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=200603280915.48793.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bharata@in.ibm.com \
--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