From: Matthew Wilcox <willy@infradead.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: David Howells <dhowells@redhat.com>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"jlayton@kernel.org" <jlayton@kernel.org>
Subject: Re: [LSF/MM/BPF TOPIC] Netfs support library
Date: Tue, 1 Feb 2022 02:32:35 +0000 [thread overview]
Message-ID: <Yfibw2kWukCyfRIK@casper.infradead.org> (raw)
In-Reply-To: <1CAF5D33-E854-4B82-AC32-0FDCF1894253@oracle.com>
On Tue, Feb 01, 2022 at 02:16:54AM +0000, Chuck Lever III wrote:
>
>
> > On Jan 31, 2022, at 4:06 PM, David Howells <dhowells@redhat.com> wrote:
> >
> > I've been working on a library (in fs/netfs/) to provide network filesystem
> > support services, with help particularly from Jeff Layton. The idea is to
> > move the common features of the VM interface, including request splitting,
> > operation retrying, local caching, content encryption, bounce buffering and
> > compression into one place so that various filesystems can share it.
>
> IIUC this suite of functions is beneficial mainly to clients,
> is that correct? I'd like to be clear about that, this is not
> an objection to the topic.
>
> I'm interested in discussing how folios might work for the
> NFS _server_, perhaps as a separate or adjunct conversation.
I'd be happy to have that discussion with you, possibly in advance of
LSFMM. I have a fortnightly Zoom call (which I put up on Youtube),
and I'd be happy to have this as a topic one week if more people are
interested than just you & I. If it's just you & me, then we can chat
any time ;-)
next prev parent reply other threads:[~2022-02-01 2:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 21:06 [LSF/MM/BPF TOPIC] Netfs support library David Howells
2022-02-01 2:16 ` Chuck Lever III
2022-02-01 2:32 ` Matthew Wilcox [this message]
2022-02-01 15:35 ` Chuck Lever III
2022-03-04 20:06 ` Steve French
2022-03-09 16:17 ` Chuck Lever III
2022-03-09 21:25 ` Steve French
2022-02-01 3:57 ` Gao Xiang
2022-02-01 13:24 ` Christian Brauner
2022-02-03 20:59 ` Steve French
2022-03-01 9:45 ` 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=Yfibw2kWukCyfRIK@casper.infradead.org \
--to=willy@infradead.org \
--cc=chuck.lever@oracle.com \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.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).