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;
MIME-Version: 1.0
References: <FF0202C3-7500-4BB3-914B-DBAA3E0EA3D7@oracle.com> <45099985-B9DE-4842-9D0F-58A5205CD81D@oracle.com>
In-Reply-To: <45099985-B9DE-4842-9D0F-58A5205CD81D@oracle.com>
From:   Amir Goldstein <amir73il@gmail.com>
Date:   Sun, 16 Apr 2023 07:20:33 +0300
Message-ID: <CAOQ4uxj8b8gV02ybuBWMu7ppBc9phrd8J_XMK_bwOYb+Z5hxCg@mail.gmail.com>
Subject: Re: [Lsf-pc] [LSF/MM/BPF TOPIC] BoF for nfsd
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>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Sat, Apr 15, 2023 at 7:35=E2=80=AFPM Chuck Lever III <chuck.lever@oracle=
.com> wrote:
>
>
> > On Apr 12, 2023, at 2:26 PM, Chuck Lever III <chuck.lever@oracle.com> w=
rote:
> >
> > 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:
> >
> >    =E2=80=A2 Progress on using iomap for NFSD READ/READ_PLUS (anna)
> >    =E2=80=A2 Replacing nfsd_splice_actor (all)
> >    =E2=80=A2 Transition from page arrays to bvecs (dhowells, hch)
> >    =E2=80=A2 tmpfs directory cookie stability (cel)
> >    =E2=80=A2 timestamp resolution and i_version (jlayton)
> >    =E2=80=A2 GSS Kerberos futures (dhowells)
> >    =E2=80=A2 NFS/NFSD CI (jlayton)
> >    =E2=80=A2 NFSD POSIX to NFSv4 ACL translation - writing down the rul=
es (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.
>
> It's been suggested that this is too many topics for a
> single session. Let me propose some ways of breaking it
> up.
>
> >    =E2=80=A2 Progress on using iomap for NFSD READ/READ_PLUS (anna)
> >    =E2=80=A2 Replacing nfsd_splice_actor
>
>
> This is probably worth its own session. We might want to
> include how to convert NFSD to use folios, or maybe that
> deserves its own conversation.
>
> >    =E2=80=A2 Transition from page arrays to bvecs (dhowells, hch)
>
>
> This is something we can take to the hallway or discuss
> over beers or a meal.
>
> >    =E2=80=A2 tmpfs directory cookie stability (cel)
>
> This could be a FS/MM session. Aside from directory
> cookies, there are issues about exporting any shmemfs-
> based filesystem (autofs is another).
>
> >    =E2=80=A2 timestamp resolution and i_version (jlayton)
>
> I'll let Jeff propose something here, and take this off
> the NFSD-specific agenda.

Please do.

>
> >    =E2=80=A2 GSS Kerberos futures (dhowells)
>
> Perhaps this topic also requires us to be drunk first.
> Seriously, though... it could be a pretty specialized
> conversation, and thus left for the hallway track.
>
> Or, David and I could fold this into the bvecs discussion
> above, as these two are somewhat related.
>
> >    =E2=80=A2 NFS/NFSD CI (jlayton)
>
> Network filesystems have special requirements for CI.
> Jeff has been working on shaping kdevops to work for
> our needs, and the work probably has broader appeal
> than only to NFS. This could be its own 30-minute session,
> or maybe we've got most everything worked out already?
>

Perhaps a guest speaker at Luis's kdevops session?

> >    =E2=80=A2 NFSD POSIX to NFSv4 ACL translation - writing down the rul=
es (all)
>
>
> Could be its own session, but it might have only a
> handful of interested parties.
>

Apropos interested parties. If there are any NFS developers/maintainers
that are interested in attending the NFSD BoF virtually, please let me know
and I will send you a code for the virtual registration option.

Thanks,
Amir.