[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1428311.1598542135@warthog.procyon.org.uk>
Date: Thu, 27 Aug 2020 16:28:55 +0100
From: David Howells <dhowells@...hat.com>
To: Christoph Hellwig <hch@....de>
Cc: dhowells@...hat.com, Alexander Viro <viro@...iv.linux.org.uk>,
Matthew Wilcox <willy@...radead.org>,
Jeff Layton <jlayton@...hat.com>,
Dave Wysochanski <dwysocha@...hat.com>,
Trond Myklebust <trondmy@...merspace.com>,
Anna Schumaker <anna.schumaker@...app.com>,
Steve French <sfrench@...ba.org>,
Eric Van Hensbergen <ericvh@...il.com>,
linux-cachefs@...hat.com, linux-afs@...ts.infradead.org,
linux-nfs@...r.kernel.org, linux-cifs@...r.kernel.org,
ceph-devel@...r.kernel.org, v9fs-developer@...ts.sourceforge.net,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] fscache rewrite -- please drop for now
Christoph Hellwig <hch@....de> wrote:
> FYI, a giant rewrite dropping support for existing consumer is always
> rather awkward. Is there any way you could pre-stage some infrastructure
> changes, and then do a temporary fscache2, which could then be renamed
> back to fscache once everyone switched over?
That's a bit tricky. There are three points that would have to be shared: the
userspace miscdev interface, the backing filesystem and the single index tree.
It's probably easier to just have a go at converting 9P and cifs. Making the
old and new APIs share would be a fairly hefty undertaking in its own right.
David
Powered by blists - more mailing lists