From: Andi Kleen <ak@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: bharata@in.ibm.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: dcache leak in 2.6.16-git8 II
Date: Thu, 30 Mar 2006 00:53:24 +0200 [thread overview]
Message-ID: <200603300053.25235.ak@suse.de> (raw)
In-Reply-To: <20060329145013.37c87323.akpm@osdl.org>
On Thursday 30 March 2006 00:50, Andrew Morton wrote:
> It looks that way. Didn't someone else report a sock_inode_cache leak?
Didn't see it.
> > I still got a copy of the /proc in case anybody wants more information.
>
> We have this fancy new /proc/slab_allocators now, it might show something
> interesting. It needs CONFIG_DEBUG_SLAB_LEAK.
I didn't have that enabled unfortunately. I can try it on the next round.
-Andi
next prev parent reply other threads:[~2006-03-29 22:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200603270750.28174.ak@suse.de>
[not found] ` <200603271822.28043.ak@suse.de>
[not found] ` <20060327190027.24498e3a.akpm@osdl.org>
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 [this message]
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=200603300053.25235.ak@suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=bharata@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).