From: Milosz Tanski <milosz@adfin.com>
To: ceph-devel@vger.kernel.org
Cc: sage@inktank.com, zheng.z.yan@intel.com
Subject: [PATCH 0/2] Fscache cleanup and fix
Date: Tue, 27 Aug 2013 19:08:31 -0400 [thread overview]
Message-ID: <cover.1377644443.git.milosz@adfin.com> (raw)
Sage,
These are the changes you requested. I eliminated the use of ifdefs in the C
code. It's all self contained in cache.[ch] and in the case of it being
disabled becomes a nop.
Also, I found a small bug where we would not free the invalidate queue on
unmount. It's split into it's own commit.
Finally, I saw that you had a hard time building it without the kernel flag
enabled. So I made sure to test a config with fscache for Ceph disabled right
before sping things.
The commits are from my branch (which is based on top of the main testing
branch) from my repo:
https://adfin@bitbucket.org/adfin/linux-fs.git branch: wip-ceph-fscache
Best,
- Milosz
Milosz Tanski (2):
ceph: Do not leak fscache workqueue
ceph: fscache cleanup
fs/ceph/cache.c | 90 ++++++++++++++++++++++++++++++++++++++++++++++++++-------
fs/ceph/cache.h | 68 +++++++++++++++++++------------------------
fs/ceph/inode.c | 61 +-------------------------------------
fs/ceph/super.c | 22 ++++----------
fs/ceph/super.h | 1 -
5 files changed, 115 insertions(+), 127 deletions(-)
--
1.8.1.2
next reply other threads:[~2013-08-27 23:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 23:08 Milosz Tanski [this message]
2013-08-27 23:08 ` [PATCH 1/2] ceph: Do not leak fscache workqueue Milosz Tanski
2013-08-27 23:09 ` [PATCH 2/2] ceph: fscache cleanup Milosz Tanski
2013-08-27 23:35 ` [PATCH 0/2] Fscache cleanup and fix Sage Weil
2013-09-02 17:44 ` Milosz Tanski
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=cover.1377644443.git.milosz@adfin.com \
--to=milosz@adfin.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.com \
--cc=zheng.z.yan@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.