From: David Howells <dhowells@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: dhowells@redhat.com, Amir Goldstein <amir73il@gmail.com>,
linux-cachefs@redhat.com, Jeff Layton <jlayton@redhat.com>,
David Wysochanski <dwysocha@redhat.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Christoph Hellwig <hch@infradead.org>,
Dave Chinner <dchinner@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-afs@lists.infradead.org,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
CIFS <linux-cifs@vger.kernel.org>,
ceph-devel <ceph-devel@vger.kernel.org>,
v9fs-developer@lists.sourceforge.net,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: fscache: Redesigning the on-disk cache
Date: Mon, 08 Mar 2021 19:08:52 +0000 [thread overview]
Message-ID: <19639.1615230532@warthog.procyon.org.uk> (raw)
In-Reply-To: <20210308185410.GE7284@fieldses.org>
J. Bruce Fields <bfields@fieldses.org> wrote:
> On Mon, Mar 08, 2021 at 09:13:55AM +0000, David Howells wrote:
> > Amir Goldstein <amir73il@gmail.com> wrote:
> > > With ->fiemap() you can at least make the distinction between a non existing
> > > and an UNWRITTEN extent.
> >
> > I can't use that for XFS, Ext4 or btrfs, I suspect. Christoph and Dave's
> > assertion is that the cache can't rely on the backing filesystem's metadata
> > because these can arbitrarily insert or remove blocks of zeros to bridge or
> > split extents.
>
> Could you instead make some sort of explicit contract with the
> filesystem? Maybe you'd flag it at mkfs time and query for it before
> allowing a filesystem to be used for fscache. You don't need every
> filesystem to support fscache, right, just one acceptable one?
I've asked about that, but the filesystem maintainers are reluctant to do
that.
Something might be possible in ext4 using direct access to jbd2, though I
don't know exactly what facilities that offers.
David
next prev parent reply other threads:[~2021-03-08 19:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 23:20 fscache: Redesigning the on-disk cache David Howells
2021-03-04 13:47 ` fscache: Redesigning the on-disk cache - LRU handling David Howells
2021-03-05 9:46 ` fscache: Redesigning the on-disk cache Amir Goldstein
2021-03-08 9:13 ` David Howells
2021-03-08 10:35 ` Amir Goldstein
2021-03-08 11:28 ` Metadata writtenback notification? -- was " David Howells
2021-03-08 22:32 ` Dave Chinner
2021-03-08 23:20 ` Matthew Wilcox
2021-03-09 11:27 ` David Howells
2021-03-08 18:54 ` J. Bruce Fields
2021-03-08 19:08 ` David Howells [this message]
2021-03-08 21:55 ` Dave Chinner
2021-03-09 9:21 ` 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=19639.1615230532@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=amir73il@gmail.com \
--cc=bfields@fieldses.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dchinner@redhat.com \
--cc=dwysocha@redhat.com \
--cc=hch@infradead.org \
--cc=jlayton@redhat.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-cachefs@redhat.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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).