From: Jeff Layton <jlayton@kernel.org>
To: ceph-devel@vger.kernel.org
Cc: dhowells@redhat.com, linux-cachefs@redhat.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] ceph: conversion to fscache API rewrite
Date: Mon, 25 Oct 2021 09:24:50 -0400 [thread overview]
Message-ID: <20211025132452.101591-1-jlayton@kernel.org> (raw)
Last week, David Howells posted a set of patches to modernize fscache
and cachefiles [1] (and in the process fix a ton of bugs). The patches
in this set convert ceph over to use the new API.
The first patch in this series switches ceph over to use the new API.
The second patch adds support for caching files that are open for write.
I've tested caching and non-caching setups with xfstests and it seems to
work well. The only remaining issue I see is that sometimes fsstress
will cause the cachefiles backend fs to fill up. When this happens, the
cache goes offline, but everything otherwise keeps working.
This is still an improvement over the existing code, however, and I
think that problem may be solveable by a more aggressive culling cycle.
[1]: https://lore.kernel.org/ceph-devel/CAHk-=wi7K64wo4PtROxq_cLhfq-c-3aCbW5CjRfnKYA439YFUw@mail.gmail.com/T/#t
Jeff Layton (2):
ceph: conversion to new fscache API
ceph: add fscache writeback support
fs/ceph/Kconfig | 2 +-
fs/ceph/addr.c | 98 +++++++++++++++++++-----
fs/ceph/cache.c | 196 +++++++++++++++++++++---------------------------
fs/ceph/cache.h | 96 +++++++++++++++++-------
fs/ceph/caps.c | 3 +-
fs/ceph/file.c | 13 +++-
fs/ceph/inode.c | 22 ++++--
fs/ceph/super.c | 10 +--
fs/ceph/super.h | 4 +-
9 files changed, 263 insertions(+), 181 deletions(-)
--
2.31.1
next reply other threads:[~2021-10-25 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-25 13:24 Jeff Layton [this message]
2021-10-25 13:24 ` [PATCH 1/2] ceph: conversion to new fscache API Jeff Layton
2021-10-25 13:24 ` [PATCH 2/2] ceph: add fscache writeback support Jeff Layton
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=20211025132452.101591-1-jlayton@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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.