Linux NFS development
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: "lsf-pc@lists.linux-foundation.org" 
	<lsf-pc@lists.linux-foundation.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [LSF/MM/BPF TOPIC] BoF for nfsd
Date: Thu, 13 Apr 2023 15:05:22 +0100	[thread overview]
Message-ID: <ZDgMIlpCwfCKcwkx@casper.infradead.org> (raw)
In-Reply-To: <FF0202C3-7500-4BB3-914B-DBAA3E0EA3D7@oracle.com>

On Wed, Apr 12, 2023 at 06:27:07PM +0000, Chuck Lever III wrote:
> I'd like to request some time for those interested specifically
> in NFSD to gather and discuss some topics. Not a network file
> system free-for-all, but specifically for NFSD, because there
> is a long list of potential topics:
> 
>     • Progress on using iomap for NFSD READ/READ_PLUS (anna)
>     • Replacing nfsd_splice_actor (all)
>     • Transition from page arrays to bvecs (dhowells, hch)

 - Using larger folios instead of single pages; maybe this is the same
   discussion.

>     • tmpfs directory cookie stability (cel)
>     • timestamp resolution and i_version (jlayton)
>     • GSS Kerberos futures (dhowells)
>     • NFS/NFSD CI (jlayton)
>     • NFSD POSIX to NFSv4 ACL translation - writing down the rules (all)
> 
> Some of these topics might be appealing to others not specifically
> involved with NFSD development. If there's something that should
> be moved to another track or session, please pipe up.
> 
> --
> Chuck Lever
> 
> 

  parent reply	other threads:[~2023-04-13 14:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 18:27 [LSF/MM/BPF TOPIC] BoF for nfsd Chuck Lever III
2023-04-13  9:33 ` Christian Brauner
2023-04-13 13:09   ` Jeff Layton
2023-04-13 17:43     ` Chuck Lever III
2023-04-13 14:05 ` Matthew Wilcox [this message]
2023-04-13 14:15   ` Chuck Lever III
2023-04-13 17:54   ` Trond Myklebust
2023-04-15 16:34 ` Chuck Lever III
2023-04-15 16:57   ` Trond Myklebust
2023-04-16  4:20   ` [Lsf-pc] " Amir Goldstein
2023-04-16 16:02     ` Chuck Lever III

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=ZDgMIlpCwfCKcwkx@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-nfs@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