Message ID | 20210126134103.240031-1-jlayton@kernel.org |
---|---|
Headers | show |
Series | ceph: convert to new netfs read helpers | expand |
On Wed, 2021-01-27 at 23:50 +0100, Ilya Dryomov wrote: > On Tue, Jan 26, 2021 at 2:41 PM Jeff Layton <jlayton@kernel.org> wrote: > > > > This patchset converts ceph to use the new netfs readpage, write_begin, > > and readahead helpers to handle buffered reads. This is a substantial > > reduction in code in ceph, but shouldn't really affect functionality in > > any way. > > > > Ilya, if you don't have any objections, I'll plan to let David pull this > > series into his tree to be merged with the netfs API patches themselves. > > Sure, that works for me. > > I would have expected that the new netfs infrastructure is pushed > to a public branch that individual filesystems could peruse, but since > David's set already includes patches for AFS and NFS, let's tag along. > > Thanks, > > Ilya David has a fscache-netfs-lib branch that has all of the infrastructure changes. See: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=fscache-netfs-lib -- Jeff Layton <jlayton@kernel.org>
On Thu, Jan 28, 2021 at 1:52 PM Jeff Layton <jlayton@kernel.org> wrote: > > On Wed, 2021-01-27 at 23:50 +0100, Ilya Dryomov wrote: > > On Tue, Jan 26, 2021 at 2:41 PM Jeff Layton <jlayton@kernel.org> wrote: > > > > > > This patchset converts ceph to use the new netfs readpage, write_begin, > > > and readahead helpers to handle buffered reads. This is a substantial > > > reduction in code in ceph, but shouldn't really affect functionality in > > > any way. > > > > > > Ilya, if you don't have any objections, I'll plan to let David pull this > > > series into his tree to be merged with the netfs API patches themselves. > > > > Sure, that works for me. > > > > I would have expected that the new netfs infrastructure is pushed > > to a public branch that individual filesystems could peruse, but since > > David's set already includes patches for AFS and NFS, let's tag along. > > > > Thanks, > > > > Ilya > > David has a fscache-netfs-lib branch that has all of the infrastructure > changes. See: > > https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=fscache-netfs-lib I saw that, but AFAICS it hasn't been declared public (as in suitable for other people to base their work on, with the promise that history won't get rewritten. It is branched off of what looks like a random snapshot of Linus' tree instead of a release point, etc. Thanks, Ilya
Ilya Dryomov <idryomov@gmail.com> wrote: > > David has a fscache-netfs-lib branch that has all of the infrastructure > > changes. See: > > > > https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=fscache-netfs-lib > > I saw that, but AFAICS it hasn't been declared public (as in suitable > for other people to base their work on, with the promise that history > won't get rewritten. My intention to avoid modifying it further, except for extra fix patches stacked on the end if necessary, as I want to try to avoid jinxing it from getting pulled in the next merge window. > It is branched off of what looks like a random snapshot of Linus' tree > instead of a release point, etc. Yeah, sorry about that. I took what was current linus/master at the time I cut the branch with the intention of trying to get it into linux-next before -rc5 was tagged (ie. >3 weeks before the merge window), but including the X.509 crash fix. David