Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 13 Apr 2023 15:05:22 +0100
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
Message-ID: <ZDgMIlpCwfCKcwkx@casper.infradead.org>
References: <FF0202C3-7500-4BB3-914B-DBAA3E0EA3D7@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <FF0202C3-7500-4BB3-914B-DBAA3E0EA3D7@oracle.com>
Precedence: bulk

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
> 
>