From: Jeff Layton <jlayton@kernel.org>
To: Christoph Hellwig <hch@infradead.org>,
David Howells <dhowells@redhat.com>
Cc: torvalds@linux-foundation.org,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
linux-mm@kvack.org, linux-cachefs@redhat.com,
linux-afs@lists.infradead.org, linux-nfs@vger.kernel.org,
linux-cifs@vger.kernel.org, ceph-devel@vger.kernel.org,
v9fs-developer@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] netfs: Add MAINTAINERS record
Date: Tue, 13 Jul 2021 07:54:36 -0400 [thread overview]
Message-ID: <f36adf661f37582b51b05c9d8d0a41ea60812b68.camel@kernel.org> (raw)
In-Reply-To: <YO0oJvuIXlcmSd7F@infradead.org>
On Tue, 2021-07-13 at 06:44 +0100, Christoph Hellwig wrote:
> On Mon, Jul 12, 2021 at 01:26:32PM +0100, David Howells wrote:
> > Add a MAINTAINERS record for the new netfs helper library.
>
> Btw, any reason why this code is called netfs? It is a library
> that seems to mostly be glue code for fscache as far as I can tell and
> has nothing to do with networking at all.
It's infrastructure for network filesystems.
The original impetus was hooking up fscache, though the helper code also
works with fscache disabled. We also have some work in progress to plumb
in fscrypt support, and David is also looking at adding
writepage/writepages support too.
readpage/readpages/writepage/writepages operations in network
filesystems are quite "fiddly", and they all do it in subtly different
ways (and not always for good reasons).
The new read helper infrastructure abstracts a lot of that away, and
gives netfs's a simpler set of operations to deal with. We're hoping to
do the same with writepage/writepages helpers soon.
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2021-07-13 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 12:26 [PATCH] netfs: Add MAINTAINERS record David Howells
2021-07-13 5:44 ` Christoph Hellwig
2021-07-13 11:54 ` Jeff Layton [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-15 16:39 David Howells
2021-06-15 15:40 David Howells
2021-06-15 16:23 ` 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=f36adf661f37582b51b05c9d8d0a41ea60812b68.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=ceph-devel@vger.kernel.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--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-mm@kvack.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=v9fs-developer@lists.sourceforge.net \
--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).