All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: mike.eisler@netapp.com, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfs(5): Replace the term "netid" in mount option descriptions
Date: Mon, 29 Sep 2008 07:53:43 -0400	[thread overview]
Message-ID: <48E0C1C7.4060201@RedHat.com> (raw)
In-Reply-To: <20080924182235.3000.71437.stgit-lQeC5l55kZ7wdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>



Chuck Lever wrote:
> TI-RPC introduced the concept of "netid" which is a string that is
> mapped to a set of transport capabilities via a netconfig database.
> RPC services register a netid and bindaddr with their local rpcbind
> daemon to advertise their ability to support particular transports.
> 
> Mike Eisler noted that the use of the term "netid" in nfs(5) is not
> appropriate, since Linux does not treat the value of the proto= or
> mountproto= options as a netid proper, but rather to select a
> particular transport capability provided locally on the client.
> 
> The Linux NFS client currently uses a simple internal mapping between
> these names and its own transport capabilities rather than using the
> names as part of an rpcbind query, thus these strings are really not
> netids.  They are more akin to what TI-RPC calls "protocol names".
> 
> Remove the term "netid" from nfs(5) for now.
> 
> Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
> Cc: Mike Eisler <mike.eisler@netapp.com>
Committed... 

steved.

      parent reply	other threads:[~2008-09-29 11:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-24 18:24 [PATCH] nfs(5): Replace the term "netid" in mount option descriptions Chuck Lever
     [not found] ` <20080924182235.3000.71437.stgit-lQeC5l55kZ7wdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2008-09-29 11:53   ` Steve Dickson [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=48E0C1C7.4060201@RedHat.com \
    --to=steved@redhat.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=mike.eisler@netapp.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.