Linux NFS development
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "dwysocha@redhat.com" <dwysocha@redhat.com>
Cc: "linux-cachefs@redhat.com" <linux-cachefs@redhat.com>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"daire.byrne@gmail.com" <daire.byrne@gmail.com>,
	"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>,
	"benmaynard@google.com" <benmaynard@google.com>,
	"dhowells@redhat.com" <dhowells@redhat.com>
Subject: Re: [RFC PATCH 2/3] NFS: Add support for netfs in struct nfs_inode and Kconfig
Date: Wed, 24 Aug 2022 13:05:06 +0000	[thread overview]
Message-ID: <da9200f1bded9b8b078a7aef227fd6b92eb028fb.camel@hammerspace.com> (raw)
In-Reply-To: <CALF+zOknvMZyufSUD-g9Z9Y5RfwE-vUFT+CF0kxqbcpR=yJPJw@mail.gmail.com>

On Wed, 2022-08-24 at 09:00 -0400, David Wysochanski wrote:
> On Wed, Aug 24, 2022 at 8:42 AM Trond Myklebust
> <trondmy@hammerspace.com> wrote:
> > 
> > On Wed, 2022-08-24 at 05:35 -0400, Dave Wysochanski wrote:
> > > As first steps for support of the netfs library, add
> > > NETFS_SUPPORT
> > > to Kconfig and add the required netfs_inode into struct
> > > nfs_inode.
> > > The struct netfs_inode is now where the vfs_inode is stored as
> > > well
> > > as the fscache_cookie.  In addition, use the netfs_inode() and
> > > netfs_i_cookie() helpers, and remove our own helper,
> > > nfs_i_fscache().
> > > 
> > > Later patches will enable netfs by defining NFS specific version
> > > of struct netfs_request_ops and calling netfs_inode_init().
> > > 
> > > Signed-off-by: Dave Wysochanski <dwysocha@redhat.com>
> > > ---
> > >  fs/nfs/Kconfig         |  1 +
> > >  fs/nfs/delegation.c    |  2 +-
> > >  fs/nfs/dir.c           |  2 +-
> > >  fs/nfs/fscache.c       | 20 +++++++++-----------
> > >  fs/nfs/fscache.h       | 15 ++++++---------
> > >  fs/nfs/inode.c         |  6 +++---
> > >  fs/nfs/internal.h      |  2 +-
> > >  fs/nfs/pnfs.c          | 12 ++++++------
> > >  fs/nfs/write.c         |  2 +-
> > >  include/linux/nfs_fs.h | 19 +++++--------------
> > >  10 files changed, 34 insertions(+), 47 deletions(-)
> > > 
> > > diff --git a/fs/nfs/Kconfig b/fs/nfs/Kconfig
> > > index 14a72224b657..79b241bed762 100644
> > > --- a/fs/nfs/Kconfig
> > > +++ b/fs/nfs/Kconfig
> > > @@ -5,6 +5,7 @@ config NFS_FS
> > >         select LOCKD
> > >         select SUNRPC
> > >         select NFS_ACL_SUPPORT if NFS_V3_ACL
> > > +       select NETFS_SUPPORT
> > > 
> > 
> > NACK. I'm not at all OK with making netfs mandatory.
> > 
> 
> Just so we're on the same page, are you ok with netfs being enabled
> if
> fscache is enabled like today?
> 

As long as it is an opt-in feature, I'm OK. I don't want to have to
compile it in by default.
A cachefs should never become a mandatory feature of networked
filesystems.

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



  reply	other threads:[~2022-08-24 13:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24  9:34 [RFC PATCH 0/3] Convert NFS to the new netfs API Dave Wysochanski
2022-08-24  9:34 ` [RFC PATCH 1/3] NFS: Rename readpage_async_filler to nfs_pageio_add_page Dave Wysochanski
2022-08-24  9:35 ` [RFC PATCH 2/3] NFS: Add support for netfs in struct nfs_inode and Kconfig Dave Wysochanski
2022-08-24 12:42   ` Trond Myklebust
2022-08-24 13:00     ` David Wysochanski
2022-08-24 13:05       ` Trond Myklebust [this message]
2022-08-24 14:12         ` David Howells
2022-08-24 16:27           ` Trond Myklebust
2022-08-24 16:53             ` Matthew Wilcox
2022-08-24 17:43               ` Trond Myklebust
2022-08-25 15:01                 ` Matthew Wilcox
2022-08-25 15:30                   ` David Howells
2022-08-25 15:32                   ` Trond Myklebust
2022-08-25 17:53                     ` Matthew Wilcox
2022-08-25 15:20             ` David Howells
2022-08-24  9:35 ` [RFC PATCH 3/3] NFS: Convert nfs_read_folio and nfs_readahead to netfs APIs Dave Wysochanski

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=da9200f1bded9b8b078a7aef227fd6b92eb028fb.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=anna.schumaker@netapp.com \
    --cc=benmaynard@google.com \
    --cc=daire.byrne@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dwysocha@redhat.com \
    --cc=linux-cachefs@redhat.com \
    --cc=linux-nfs@vger.kernel.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