From mboxrd@z Thu Jan 1 00:00:00 1970 From: Balbir Singh Subject: Re: dcache leak in 2.6.16-git8 II Date: Thu, 30 Mar 2006 12:11:04 +0530 Message-ID: <20060330064104.GC18387@in.ibm.com> References: <200603270750.28174.ak@suse.de> <200603300026.59131.ak@suse.de> <20060329145013.37c87323.akpm@osdl.org> <200603300053.25235.ak@suse.de> Reply-To: balbir@in.ibm.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Andrew Morton , bharata@in.ibm.com, linux-kernel@vger.kernel.org, netdev@vger.kernel.org Return-path: To: Andi Kleen Content-Disposition: inline In-Reply-To: <200603300053.25235.ak@suse.de> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Thu, Mar 30, 2006 at 12:53:24AM +0200, Andi Kleen wrote: > 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 > There is also a new sysctl to drop caches. It is called vm.drop_caches. It will be interesting to see if it is able to free up some dcache memory for you. Balbir