From: Jeff Layton <jlayton@kernel.org>
To: ceph-devel@vger.kernel.org
Cc: idryomov@gmail.com, dhowells@redhat.com,
linux-fsdevel@vger.kernel.org, linux-cachefs@redhat.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] ceph: adapt ceph to the fscache rewrite
Date: Mon, 29 Nov 2021 11:29:05 -0500 [thread overview]
Message-ID: <20211129162907.149445-1-jlayton@kernel.org> (raw)
This is a follow-on set for David Howells' recent patchset to rewrite
the fscache and cachefiles infrastructure. This re-enables fscache read
support in the ceph driver, and also adds support for writing to the
cache as well.
What's the best way to handle these, going forward? David, would it be
easier for you to carry these in your tree along with the rest of your
series?
Jeff Layton (2):
ceph: conversion to new fscache API
ceph: add fscache writeback support
fs/ceph/Kconfig | 2 +-
fs/ceph/addr.c | 99 +++++++++++++++++++------
fs/ceph/cache.c | 188 ++++++++++++++++++++----------------------------
fs/ceph/cache.h | 98 +++++++++++++++++--------
fs/ceph/caps.c | 3 +-
fs/ceph/file.c | 13 +++-
fs/ceph/inode.c | 22 ++++--
fs/ceph/super.c | 10 +--
fs/ceph/super.h | 2 +-
9 files changed, 255 insertions(+), 182 deletions(-)
--
2.33.1
next reply other threads:[~2021-11-29 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 16:29 Jeff Layton [this message]
2021-11-29 16:29 ` [PATCH 1/2] ceph: conversion to new fscache API Jeff Layton
2021-11-29 16:29 ` [PATCH 2/2] ceph: add fscache writeback support Jeff Layton
2021-11-29 16:46 ` [PATCH 1/2] ceph: conversion to new fscache API David Howells
2021-12-01 11:31 ` Jeff Layton
2021-12-06 9:57 ` David Howells
2021-12-06 10:59 ` Jeff Layton
2021-12-06 11:12 ` [PATCH 2/2] ceph: add fscache writeback support David Howells
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=20211129162907.149445-1-jlayton@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=idryomov@gmail.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 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).