From: Sage Weil <sage@newdream.net>
To: linux-fsdevel@vger.kernel.org, viro@ZenIV.linux.org.uk
Cc: hch@infradead.org, ceph-devel@vger.kernel.org,
rwheeler@redhat.com, linux-kernel@vger.kernel.org,
Sage Weil <sage@newdream.net>
Subject: [PATCH] d_prune dentry_operation
Date: Wed, 5 Oct 2011 21:26:09 -0700 [thread overview]
Message-ID: <1317875170-9349-1-git-send-email-sage@newdream.net> (raw)
Ceph goes to great lengths to keep its client-side cache coherent,
allowing many operations (lookup, creations, readdir) to be performed
without any server interaction when the client has the proper leases.
Sadly, this functionality is all currently disabled because we cannot
handle races between dcache pruning and any of those activities with the
current VFS interface.
This patch adds a d_prune hook that allows the filesystem to be informed
before a dentry is removed from the cache. Merging this for 3.2-rc1
will make Ceph users and their metadata-intensive workload very happy.
If anybody has any issues at all with this, please tell me, so I can
make my case or revise my approach.
Thanks!
sage
Sage Weil (1):
vfs: add d_prune dentry operation
Documentation/filesystems/Locking | 1 +
fs/dcache.c | 8 ++++++++
include/linux/dcache.h | 3 +++
3 files changed, 12 insertions(+), 0 deletions(-)
--
1.7.2.5
next reply other threads:[~2011-10-06 4:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-06 4:26 Sage Weil [this message]
2011-10-06 4:26 ` [PATCH] vfs: add d_prune dentry operation Sage Weil
2011-10-06 21:21 ` Christoph Hellwig
2011-10-06 22:20 ` Sage Weil
2011-10-09 13:21 ` Christoph Hellwig
2011-10-10 5:11 ` Dave Chinner
2011-10-10 11:23 ` Christoph Hellwig
2011-10-10 16:19 ` Sage Weil
2011-10-10 16:21 ` Christoph Hellwig
2011-10-11 15:39 ` Sage Weil
2011-10-11 21:56 ` Dave Chinner
2011-10-28 12:16 ` Christoph Hellwig
2011-10-28 17:02 ` Sage Weil
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=1317875170-9349-1-git-send-email-sage@newdream.net \
--to=sage@newdream.net \
--cc=ceph-devel@vger.kernel.org \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rwheeler@redhat.com \
--cc=viro@ZenIV.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).