From: Glauber Costa <glommer@parallels.com>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org,
containers@lists.linux-foundation.org,
Pavel Emelyanov <xemul@parallels.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Hugh Dickins <hughd@google.com>, Nick Piggin <npiggin@kernel.dk>,
Andrea Arcangeli <aarcange@redhat.com>,
Rik van Riel <riel@redhat.com>,
Dave Hansen <dave@linux.vnet.ibm.com>,
James Bottomley <JBottomley@parallels.com>,
David Chinner <david@fromorbit.com>,
Glauber Costa <glommer@parallels.com>
Subject: [PATCH v2 0/4] Per-container dcache size limitation
Date: Fri, 5 Aug 2011 04:35:40 +0400 [thread overview]
Message-ID: <1312504544-1108-1-git-send-email-glommer@parallels.com> (raw)
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(-)
--
1.7.6
next reply other threads:[~2011-08-05 0:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 0:35 Glauber Costa [this message]
2011-08-05 0:35 ` [PATCH v2 1/4] factor out single-shrinker code Glauber Costa
2011-08-05 0:35 ` [PATCH v2 2/4] Keep nr_dentry per super block Glauber Costa
2011-08-12 13:51 ` Eric Dumazet
2011-08-05 0:35 ` [PATCH v2 3/4] limit nr_dentries per superblock Glauber Costa
2011-08-12 13:56 ` Eric Dumazet
2011-08-12 19:18 ` Glauber Costa
2011-08-12 19:20 ` Glauber Costa
2011-08-05 0:35 ` [PATCH v2 4/4] parse options in the vfs level Glauber Costa
2011-08-12 10:52 ` [PATCH v2 0/4] Per-container dcache size limitation Glauber Costa
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=1312504544-1108-1-git-send-email-glommer@parallels.com \
--to=glommer@parallels.com \
--cc=JBottomley@parallels.com \
--cc=aarcange@redhat.com \
--cc=containers@lists.linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=david@fromorbit.com \
--cc=hughd@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@kernel.dk \
--cc=riel@redhat.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@parallels.com \
/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
Powered by JetHome