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 0/4] Per-superblock dcache limitation
Date: Fri, 29 Jul 2011 17:44:15 +0400 [thread overview]
Message-ID: <1311947059-17209-1-git-send-email-glommer@parallels.com> (raw)
Hello,
Now that we've got per-sb dcache lru lists, I am proposing
through theses patches that each of those be size-limited.
The main use case I am targetting is containers, where we want
a container not to use more than a certain specified amount
of non-shrikable kernel memory.
Comments welcome
Glauber Costa (4):
Keep nr_dentry per super block
limit nr_dentries per superblock
dcache set size
parse options in the vfs level
fs/dcache.c | 75 +++++++++++++++++++++++++++++++---------
fs/namespace.c | 89 ++++++++++++++++++++++++++++++++++++++++++++++++
fs/super.c | 3 ++
include/linux/dcache.h | 1 +
include/linux/fs.h | 3 ++
5 files changed, 155 insertions(+), 16 deletions(-)
--
1.7.6
next reply other threads:[~2011-07-29 13:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-29 13:44 Glauber Costa [this message]
2011-07-29 13:44 ` [PATCH 1/4] Keep nr_dentry per super block Glauber Costa
2011-07-31 0:50 ` Dave Chinner
2011-07-29 13:44 ` [PATCH 2/4] limit nr_dentries per superblock Glauber Costa
2011-07-31 1:15 ` Dave Chinner
2011-08-02 12:46 ` Glauber Costa
2011-07-29 13:44 ` [PATCH 3/4] dcache set size Glauber Costa
2011-07-31 1:38 ` Dave Chinner
2011-07-29 13:44 ` [PATCH 4/4] parse options in the vfs level Glauber Costa
2011-07-31 1:34 ` Dave Chinner
2011-08-02 13:04 ` Glauber Costa
2011-08-02 14:18 ` Al Viro
2011-08-02 14:43 ` 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=1311947059-17209-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
all inboxes | Powered by JetHome®