From: Dave Chinner <david@fromorbit.com>
To: Benjamin Coddington <bcodding@redhat.com>
Cc: xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org,
linux-nfs@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christoph Hellwig <hch@lst.de>,
bfields@fieldses.org
Subject: Re: [PATCH 2/2] abstract block export operations from nfsd layouts
Date: Sat, 9 Jul 2016 09:30:03 +1000 [thread overview]
Message-ID: <20160708233003.GO27480@dastard> (raw)
In-Reply-To: <EAD93DB0-20FD-4EC5-9232-F12671E21630@redhat.com>
On Fri, Jul 08, 2016 at 09:24:27AM -0400, Benjamin Coddington wrote:
> On 7 Jul 2016, at 18:38, Dave Chinner wrote:
>
> > On Thu, Jul 07, 2016 at 07:02:32AM -0400, Benjamin Coddington wrote:
> >> Instead of creeping pnfs layout configuration into filesystems, move the
> >> definition of block-based export operations under a more abstract
> >> configuration.
> >>
> >> Signed-off-by: Benjamin Coddington <bcodding@redhat.com>
> >> ---
> >> fs/Kconfig | 3 +++
> >> fs/nfsd/Kconfig | 2 ++
> >> fs/xfs/Makefile | 3 +--
> >> fs/xfs/xfs_export.c | 2 +-
> >> fs/xfs/xfs_pnfs.h | 4 ++--
> >> 5 files changed, 9 insertions(+), 5 deletions(-)
> >>
> >> diff --git a/fs/Kconfig b/fs/Kconfig
> >> index 6725f59c18e6..6e57b4237d72 100644
> >> --- a/fs/Kconfig
> >> +++ b/fs/Kconfig
> >> @@ -66,6 +66,9 @@ config FS_POSIX_ACL
> >> config EXPORTFS
> >> tristate
> >>
> >> +config BLOCK_EXPORT_OPS
> >> + bool
> >> +
> >
> > default n, help text?
>
> Not set is n, and as it isn't visible or intended to be set by a user, I
> left out the help text. I'll add both for completeness.
>
> > Also, BLOCK_* prefix config options are for block layer
> > functionality, hence I suspect this will confuse people because it's
> > a filesystem config option. EXPORTFS_BLOCK_OPS seems more obvious
> > and correct to me, as the block mapping ops are part of the exportfs
> > operations interface....
>
> OK. I agree - that is better.
>
> >> xfs-$(CONFIG_SYSCTL) += xfs_sysctl.o
> >> xfs-$(CONFIG_COMPAT) += xfs_ioctl32.o
> >> -xfs-$(CONFIG_NFSD_BLOCKLAYOUT) += xfs_pnfs.o
> >> -xfs-$(CONFIG_NFSD_SCSILAYOUT) += xfs_pnfs.o
> >> +xfs-$(CONFIG_BLOCK_EXPORT_OPS) += xfs_pnfs.o
> >
> > Why do we need the first patch to XFS anymore? Just convert it
> > straight to using CONFIG_EXPORTFS_BLOCK_OPS....
>
> Doing this in a single patch would combine two changes in a single commit:
> - the definition of the extra operations for a config of only SCSI_LAYOUT
> - the addition of CONFIG_EXPORTFS_BLOCK_OPS.
>
> Since the first is the originally intended behavior, and the second fixes it
> up, I'll just send it along in a single patch if that's preferred.
prev parent reply other threads:[~2016-07-08 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-07 11:02 [PATCH 1/2] nfsd: allow SCSI layout support without block layout Benjamin Coddington
2016-07-07 11:02 ` [PATCH 2/2] xfs: abstract block export operations from nfsd layouts Benjamin Coddington
2016-07-07 15:43 ` J. Bruce Fields
2016-07-07 22:38 ` Dave Chinner
2016-07-08 13:24 ` [PATCH 2/2] " Benjamin Coddington
2016-07-08 23:30 ` Dave Chinner [this message]
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=20160708233003.GO27480@dastard \
--to=david@fromorbit.com \
--cc=bcodding@redhat.com \
--cc=bfields@fieldses.org \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=xfs@oss.sgi.com \
/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