On Tue, Nov 12, 2013 at 04:32:51PM -0800, Marc Eshel wrote: > "J. Bruce Fields" <bfields@xxxxxxxxxxxx> wrote on 11/12/2013 03:02:01 PM: > > > From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx> > > To: Marc Eshel/Almaden/IBM@IBMUS, > > Cc: Anna Schumaker <bjschuma@xxxxxxxxxx>, linux-nfs@xxxxxxxxxxxxxxx, > > linux-nfs-owner@xxxxxxxxxxxxxxx > > Date: 11/12/2013 03:19 PM > > Subject: Re: [PATCH v2 0/3] NFSD: Implement SEEK > > > > On Tue, Nov 12, 2013 at 02:44:21PM -0800, Marc Eshel wrote: > > > linux-nfs-owner@xxxxxxxxxxxxxxx wrote on 11/12/2013 11:45:29 AM: > > > > > > > From: "J. Bruce Fields" <bfields@xxxxxxxxxxxx> > > > > To: Anna Schumaker <bjschuma@xxxxxxxxxx>, > > > > Cc: linux-nfs@xxxxxxxxxxxxxxx > > > > Date: 11/12/2013 12:07 PM > > > > Subject: Re: [PATCH v2 0/3] NFSD: Implement SEEK > > > > Sent by: linux-nfs-owner@xxxxxxxxxxxxxxx > > > > > > > > On Tue, Nov 12, 2013 at 02:04:05PM -0500, Anna Schumaker wrote: > > > > > These patches implement just the SEEK NFS v4.2 operation. > WRITE_PLUS > > > is > > > > > still under discussion with the IETF after my last series of > patches, > > > so I > > > > > am holding off on resubmitting until after spec discussion dies > down. > > > > > > > > > > Questions? Comments? Thoughts? > > > > > Anna > > > > > > > > > > Anna Schumaker (3): > > > > > NFSD: Update error codes > > > > > > > > I don't think I got this first patch. > > > > > > > > > NFSD: Create nfs v4.2 decode ops > > > > > NFSD: Implement SEEK > > > > > > > > I'd like to be reassured the protocol is reasonably stable before we > > > > commit this. I haven't been following the ietf wg discussion > closely. > > > > > > > > And this should initially be disabled by default. So, probably > either: > > > > > > It is not enough that it is usable only for client the mount > > > minorversion=2 > > > anyone using this option knows that they are using a prototype. > > > > The client may default to minorversion=2 some day, so, no, the user > > doesn't necessarily know they're using a prototype. > > > > And the server doesn't have any control over what kernel or distro the > > client's running. We want future clients to be able to default to 4.2, > > and we don't require servers and clients to be upgraded in lockstep. > > The server accepting 4.2 mount can be under config options but once it is > mounted it can support the new features by checking for the the version, > right? Sorry, I don't understand the question. --b. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
