Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsd: default NFSv4.2 to on
Date: Wed, 11 Feb 2015 09:12:57 -0500	[thread overview]
Message-ID: <20150211141257.GA25696@fieldses.org> (raw)
In-Reply-To: <20150211123757.GA10532@infradead.org>

On Wed, Feb 11, 2015 at 04:37:57AM -0800, Christoph Hellwig wrote:
> On Mon, Feb 02, 2015 at 11:15:57AM -0500, J. Bruce Fields wrote:
> > From: "J. Bruce Fields" <bfields@redhat.com>
> > 
> > The code seems to work.  The protocol looks stable.  The kernel's
> > version defaults can be overridden by rpc.nfsd arguments.
> 
> Does it really make sense to enabled this without READ_PLUS support
> or implementing the various new attributes?

I think so.  That's all optional--e.g. for READ_PLUS clients can
determine server support using ERR_OP_NOTSUPP (or whatever it's called),
and for attributes they can query the supported_attributes attribute.
It's possible we'll never support everything in 4.2.

> Also should we add a wiki page with the 4.2 status?

Sounds like a good idea.

--b.

  reply	other threads:[~2015-02-11 14:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 16:15 [PATCH] nfsd: default NFSv4.2 to on J. Bruce Fields
2015-02-11 12:37 ` Christoph Hellwig
2015-02-11 14:12   ` J. Bruce Fields [this message]
2015-02-11 14:16     ` Christoph Hellwig
2015-02-11 14:54       ` J. Bruce Fields
2015-02-11 15:15         ` Trond Myklebust
2015-02-11 15:32           ` J. Bruce Fields
2015-02-11 18:12         ` Tom Haynes
2015-02-11 18:27           ` J. Bruce Fields

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=20150211141257.GA25696@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=hch@infradead.org \
    --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