From: Christoph Hellwig <hch@lst.de>
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>,
Dave Chinner <david@fromorbit.com>,
Christoph Hellwig <hch@lst.de>,
bfields@fieldses.org
Subject: Re: [PATCH v2] xfs: abstract block export operations from nfsd layouts
Date: Sun, 10 Jul 2016 11:45:40 +0200 [thread overview]
Message-ID: <20160710094540.GA19392@lst.de> (raw)
In-Reply-To: <6c1549ee874431c8293cad72c5f7382095277822.1467985684.git.bcodding@redhat.com>
On Fri, Jul 08, 2016 at 09:53:20AM -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.
>
> Changes from v1:
> - dropped the first patch in the first posting
> - renamed the config to EXPORTFS_BLOCK_OPS from BLOCK_EXPORT_OPS
> - add an explicit default to no for EXPORTFS_BLOCK_OPS
> - add some help and menu text
>
> Signed-off-by: Benjamin Coddington <bcodding@redhat.com>
> ---
> fs/Kconfig | 7 +++++++
> fs/nfsd/Kconfig | 2 ++
> fs/xfs/Makefile | 3 +--
> fs/xfs/xfs_export.c | 2 +-
> fs/xfs/xfs_pnfs.h | 4 ++--
> 5 files changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/fs/Kconfig b/fs/Kconfig
> index 6725f59c18e6..ac6d3b36600c 100644
> --- a/fs/Kconfig
> +++ b/fs/Kconfig
> @@ -66,6 +66,13 @@ config FS_POSIX_ACL
> config EXPORTFS
> tristate
>
> +config EXPORTFS_BLOCK_OPS
> + bool "Enable filesystem export operations for block IO"
> + default n
default n is the default, no need to add it.
Otherwise looks fine:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2016-07-10 9:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 13:53 [PATCH v2] xfs: abstract block export operations from nfsd layouts Benjamin Coddington
2016-07-10 9:45 ` Christoph Hellwig [this message]
2016-07-13 20:21 ` J. Bruce Fields
2016-07-13 23:23 ` Dave Chinner
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=20160710094540.GA19392@lst.de \
--to=hch@lst.de \
--cc=bcodding@redhat.com \
--cc=bfields@fieldses.org \
--cc=david@fromorbit.com \
--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;
as well as URLs for NNTP newsgroup(s).