[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4E4505F9.1040609@parallels.com>
Date: Fri, 12 Aug 2011 07:52:41 -0300
From: Glauber Costa <glommer@...allels.com>
To: Glauber Costa <glommer@...allels.com>
CC: <linux-kernel@...r.kernel.org>, <linux-fsdevel@...r.kernel.org>,
<containers@...ts.linux-foundation.org>,
Pavel Emelyanov <xemul@...allels.com>,
Al Viro <viro@...iv.linux.org.uk>,
Hugh Dickins <hughd@...gle.com>,
Nick Piggin <npiggin@...nel.dk>,
Andrea Arcangeli <aarcange@...hat.com>,
Rik van Riel <riel@...hat.com>,
Dave Hansen <dave@...ux.vnet.ibm.com>,
James Bottomley <JBottomley@...allels.com>,
David Chinner <david@...morbit.com>
Subject: Re: [PATCH v2 0/4] Per-container dcache size limitation
On 08/04/2011 09:35 PM, Glauber Costa wrote:
> Hi,
>
> Since v1, there is not too much new here.
> I'm incorporating David's suggestion of calling the sb
> shrinker, which will, in effect, prune the icache and
> other sb related objects as well.
>
> I am also keeping the mount based interface, since I
> still believe it is the way to go. But I'm obviously
> still open for suggestions. Some small corrections
> were also made to it since v1. Specifically, bind
> mounts are not allowed to alter the original sb dcache
> size.
>
> Glauber Costa (4):
> factor out single-shrinker code
> Keep nr_dentry per super block
> limit nr_dentries per superblock
> parse options in the vfs level
>
> fs/dcache.c | 44 +++++++++++-
> fs/namespace.c | 105 ++++++++++++++++++++++++++
> fs/super.c | 16 ++++-
> include/linux/dcache.h | 4 +
> include/linux/fs.h | 3 +
> include/linux/shrinker.h | 6 ++
> mm/vmscan.c | 185 ++++++++++++++++++++++++----------------------
> 7 files changed, 274 insertions(+), 89 deletions(-)
>
People,
Any comments on this? I think I addressed all the comments previously
made, and if there are no further requests, I think this is ready for
getting in. In case there are issues, please let me know so I can
address them.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists