From: "J. Bruce Fields" <bfields@fieldses.org>
To: Thomas Haynes <loghyr@primarydata.com>
Cc: hch <hch@lst.de>, Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 4/4] nfsd: Provide a config option for flex file layouts
Date: Wed, 25 May 2016 14:21:44 -0400 [thread overview]
Message-ID: <20160525182144.GC12306@fieldses.org> (raw)
In-Reply-To: <5F7AEB38-6AFE-4BB5-B52A-3EF358FF5B46@primarydata.com>
On Wed, May 25, 2016 at 06:19:20PM +0000, Thomas Haynes wrote:
>
> > On May 25, 2016, at 8:09 AM, Christoph Hellwig <hch@lst.de> wrote:
> >
> >> +config NFSD_FLEXFILELAYOUT
> >> + bool "NFSv4.1 server support for pNFS Flex File layouts"
> >> + depends on NFSD_V4
> >> + select NFSD_PNFS
> >> + help
> >> + This option enables support for the exporting pNFS Flex File
> >> + layouts in the kernel's NFS server. The pNFS Flex File layout
> >> + enables NFS clients to directly perform I/O to NFSv3 devices
> >> + accesible to both the server and the clients. See
> >> + draft-ietf-nfsv4-flex-files for more details.
> >
> > How about a bit more of a warning that this is just a toy demo server?
> >
>
> Add:
>
> Warning, this server implements the bare minimum functionality for
> to be a flex file server - it is more for testing the client
> than for a production server.
I'd leave out the "more", and just say "it is for testing the client,
not for use in production".
Which makes me wonder whether it's even worth merging.
But it's very small and self-contained, so I'm inclined to go ahead,
pending other review.
--b.
prev parent reply other threads:[~2016-05-25 18:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-25 5:09 [PATCH 0/4] Super simple flex file server Tom Haynes
2016-05-25 5:09 ` [PATCH 1/4] nfsd: flex file device id encoding will need the server addres Tom Haynes
2016-05-25 11:49 ` Jeff Layton
2016-05-25 15:08 ` Christoph Hellwig
2016-05-25 5:09 ` [PATCH 2/4] nfsd: Can leak pnfs_block_extent on error Tom Haynes
2016-05-25 11:50 ` Jeff Layton
2016-05-25 15:07 ` Christoph Hellwig
2016-05-25 18:12 ` Thomas Haynes
2016-05-25 18:20 ` J. Bruce Fields
2016-05-25 5:09 ` [PATCH 3/4] nfsd: Add a super simple flex file server Tom Haynes
2016-05-25 12:00 ` Jeff Layton
2016-05-25 12:30 ` Jeff Layton
2016-05-25 14:41 ` Thomas Haynes
2016-05-25 17:42 ` J. Bruce Fields
2016-05-25 21:57 ` Jeff Layton
2016-05-26 13:18 ` J. Bruce Fields
2016-05-25 15:15 ` Christoph Hellwig
2016-05-26 5:37 ` Thomas Haynes
2016-05-25 5:09 ` [PATCH 4/4] nfsd: Provide a config option for flex file layouts Tom Haynes
2016-05-25 15:09 ` Christoph Hellwig
2016-05-25 18:19 ` Thomas Haynes
2016-05-25 18:21 ` J. Bruce Fields [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=20160525182144.GC12306@fieldses.org \
--to=bfields@fieldses.org \
--cc=hch@lst.de \
--cc=linux-nfs@vger.kernel.org \
--cc=loghyr@primarydata.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.