linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux NFS Mailing list <linux-nfs@vger.kernel.org>,
	Linux NFSv4 mailing list <nfsv4@linux-nfs.org>
Subject: Re: [PATCH 2/2] Enable v4 mounts when either "nfsvers=4" or "vers=4" option are set (vers-02)
Date: Wed, 26 Aug 2009 13:08:02 -0400	[thread overview]
Message-ID: <4A956BF2.6000902@RedHat.com> (raw)
In-Reply-To: <23199F1A-EA23-4DE1-AAB8-92D4B508C865@oracle.com>

On 08/26/2009 12:35 PM, Chuck Lever wrote: 
> On Aug 26, 2009, at 11:07 AM, Steve Dickson wrote:
>>> I think that would be a much better approach.  If nfs4 goes away
>>> someday, for example, it will be completely transparent to the mount
>>> command if we've already pushed "-t nfs, vers=4" conversion into the
>>> kernel.
>> Well when/if that day comes, we can easily pull the patches from the
>> mount
>> command.
> 
> You know it's never that easy.  The mount command has to keep legacy
> logic for older kernels.  I'm just saying that the less the mount
> command has to worry about what kernel version is running, the cleaner
> the mount command will be.
Well with this patch, since we are only concentrating on text mounts,
we are already breaking with the tradition of keeping legacy logic... 
And again as long as the nfs4 file system exists this approach will work... 
 
> 
>>> We are pushing all of the details of NFS mounting into the kernel
>>> anyway, over time.
>> Which I've never been a fan of... Again it's much easier change user
>> level code (and more people can do it) than kernel code... especially
>> with things of this nature...
> 
> People can continue to change the mount command all they want.  In fact
> the user space text-based option parsing code is pretty darn flexible as
> it is now.
Yes... the user space parsing code is very well written... 

> 
> I don't think we're denying that your proposal is expedient.  The
> question I think is where we want to be in the long run, 
NFS v4 as the default protocol version followed by NFS V4.1 becoming the
default protocol version. 

> and if your proposed method to handle -t nfs -o vers=4 will make 
> it more complicated to get there.
No. I'm proposing a simple shorthand patch that will make mounting nfs4
file systems easier in hope of moving the technology forward by making 
it more accessible... What I believe you are proposing is architecture
change to hide the fact nfs and nfs4 are separate file systems... 

But in the end, if we do the simple shorthand patch (making the technology 
available today) or the major architecture change (making the technology
available the distant future) with both approaches 'mount -o v4' 
will do the exact same thing... 

I for moving the technology today... 

steved.

  reply	other threads:[~2009-08-26 17:08 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25 17:52 [PATCH 0/2] Enable v4 mounts when either "nfsvers=4" or "vers=4" option are set (vers-02) Steve Dickson
2009-08-25 17:54 ` [PATCH 1/2] " Steve Dickson
     [not found] ` <4A9424DB.2040303-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-08-25 17:55   ` [PATCH 2/2] " Steve Dickson
2009-08-25 18:59     ` Chuck Lever
2009-08-25 19:18       ` Steve Dickson
2009-08-25 19:32         ` Chuck Lever
2009-08-25 20:15           ` Steve Dickson
2009-08-25 20:37             ` Chuck Lever
2009-08-26 12:10               ` Steve Dickson
2009-08-25 20:49             ` Trond Myklebust
2009-08-26 12:28               ` Steve Dickson
2009-08-26 14:20               ` Chuck Lever
2009-08-26 15:07                 ` Steve Dickson
2009-08-26 16:35                   ` Chuck Lever
2009-08-26 17:08                     ` Steve Dickson [this message]
2009-08-26 17:22                       ` Chuck Lever
2009-08-26 17:51                         ` Steve Dickson
2009-08-26 19:50                           ` Chuck Lever
2009-08-26 19:59                             ` Trond Myklebust
2009-08-27 14:14                               ` Steve Dickson
2009-08-27 17:32                                 ` Chuck Lever
2009-08-28  2:55                                   ` Steve Dickson
2009-08-28 16:12                                   ` Christoph Hellwig
2009-08-28 16:35                                     ` Steve Dickson
     [not found]                                       ` <4A980751.7070206-AfCzQyP5zfLQT0dZR+AlfA@public.gmane.org>
2009-08-28 16:41                                         ` Christoph Hellwig
2009-08-28 16:44                                           ` Chuck Lever
2009-08-28 16:53                                           ` Steve Dickson
2009-08-28 16:59                                             ` Christoph Hellwig
2009-08-28 17:19                                               ` Steve Dickson
2009-08-27 17:48                                 ` Trond Myklebust
2009-08-27 17:58                                   ` Chuck Lever
2009-08-27 19:28                                     ` Steve Dickson

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=4A956BF2.6000902@RedHat.com \
    --to=steved@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=nfsv4@linux-nfs.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;
as well as URLs for NNTP newsgroup(s).