From mboxrd@z Thu Jan 1 00:00:00 1970 From: Cyrill Gorcunov Subject: Re: [patch 0/3] A few patches for dcache Date: Fri, 29 Jul 2011 09:59:18 +0400 Message-ID: <20110729055918.GB15883@sun> References: <20110728131219.146414619@openvz.org> <20110729032503.GD5404@dastard> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Al Viro , LINUXFS-ML , Andrew Morton , Christoph Hellwig , James Bottomley , xemul@openvz.org To: Dave Chinner Return-path: Received: from mail-fx0-f46.google.com ([209.85.161.46]:60429 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754432Ab1G2F7X (ORCPT ); Fri, 29 Jul 2011 01:59:23 -0400 Received: by fxh19 with SMTP id 19so1960407fxh.19 for ; Thu, 28 Jul 2011 22:59:22 -0700 (PDT) Content-Disposition: inline In-Reply-To: <20110729032503.GD5404@dastard> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Jul 29, 2011 at 01:25:03PM +1000, Dave Chinner wrote: ... > > The VFS shrinker code is now already called on a per-sb basis. Each > sb has it's own shrinker context that deals with dentries, inodes > and anything a filesystem wants to have shrunk in the call. That > solves the original issue I had with your "limit the dentry cache > size" patch series in that it didn't shrink or limit the other VFS > caches that were the ones that were really consuming all your > memory... Thanks for comments, Dave! Still the read only lock without increasing sequence number might be useful, no? (patch 1) ... > > Dave. Cyrill