Linux NFS development
 help / color / mirror / Atom feed
From: James Lentini <jlentini@netapp.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	Thomas Talpey <talpey@netapp.com>,
	Tom Tucker <tom@opengridcomputing.com>,
	Chuck Lever <chuck.lever@oracle.com>,
	linux-nfs@vger.kernel.org
Subject: Re: [PATCH] update NFS/RDMA documentation
Date: Mon, 2 Jun 2008 16:25:02 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0806021624440.26788@jlentini-linux.nane.netapp.com> (raw)
In-Reply-To: <20080602200243.GB27583@fieldses.org>



On Mon, 2 Jun 2008, J. Bruce Fields wrote:

> On Mon, Jun 02, 2008 at 03:33:59PM -0400, James Lentini wrote:
> > 
> > Bruce,
> > 
> > Below is an update to the NFS/RDMA documentation that clarifies how to 
> > run mount.nfs and addresses comments from you and Chuck. Could you 
> > please merge this for 2.6.26?
> 
> Yep, thanks.
> 
> Mind if we keep this wrapped at under 80 characters?

Sounds good.

> 
> --b.
> 
> commit 80d7681a66c1d800fd6a8e03346219f5e8de185d
> Author: J. Bruce Fields <bfields@citi.umich.edu>
> Date:   Mon Jun 2 16:01:51 2008 -0400
> 
>     nfs: rewrap NFS/RDMA documentation to 80 lines
>     
>     Wrap long lines.
>     
>     Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
> 
> diff --git a/Documentation/filesystems/nfs-rdma.txt b/Documentation/filesystems/nfs-rdma.txt
> index 9ad453d..44bd766 100644
> --- a/Documentation/filesystems/nfs-rdma.txt
> +++ b/Documentation/filesystems/nfs-rdma.txt
> @@ -63,10 +63,10 @@ Installation
>    - Install nfs-utils-1.1.2 or greater on the client
>  
>      An NFS/RDMA mount point can be obtained by using the mount.nfs command in
> -    nfs-utils-1.1.2 or greater (nfs-utils-1.1.1 was the first nfs-utils version
> -    with support for NFS/RDMA mounts, but for various reasons we recommend using
> -    nfs-utils-1.1.2 or greater). To see which version of mount.nfs you are
> -    using, type:
> +    nfs-utils-1.1.2 or greater (nfs-utils-1.1.1 was the first nfs-utils
> +    version with support for NFS/RDMA mounts, but for various reasons we
> +    recommend using nfs-utils-1.1.2 or greater). To see which version of
> +    mount.nfs you are using, type:
>  
>      $ /sbin/mount.nfs -V
>  
> @@ -91,8 +91,9 @@ Installation
>  
>      After building the nfs-utils package, there will be a mount.nfs binary in
>      the utils/mount directory. This binary can be used to initiate NFS v2, v3,
> -    or v4 mounts. To initiate a v4 mount, the binary must be called mount.nfs4.
> -    The standard technique is to create a symlink called mount.nfs4 to mount.nfs.
> +    or v4 mounts. To initiate a v4 mount, the binary must be called
> +    mount.nfs4.  The standard technique is to create a symlink called
> +    mount.nfs4 to mount.nfs.
>  
>      This mount.nfs binary should be installed at /sbin/mount.nfs as follows:
>  
> @@ -214,11 +215,11 @@ NFS/RDMA Setup
>      /vol0   192.168.0.47(fsid=0,rw,async,insecure,no_root_squash)
>      /vol0   192.168.0.0/255.255.255.0(fsid=0,rw,async,insecure,no_root_squash)
>  
> -    The IP address(es) is(are) the client's IPoIB address for an InfiniBand HCA or the
> -    cleint's iWARP address(es) for an RNIC.
> +    The IP address(es) is(are) the client's IPoIB address for an InfiniBand
> +    HCA or the cleint's iWARP address(es) for an RNIC.
>  
> -    NOTE: The "insecure" option must be used because the NFS/RDMA client does not
> -    use a reserved port.
> +    NOTE: The "insecure" option must be used because the NFS/RDMA client does
> +    not use a reserved port.
>  
>   Each time a machine boots:
>  
> @@ -234,12 +235,13 @@ NFS/RDMA Setup
>  
>    - Start the NFS server
>  
> -    If the NFS/RDMA server was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in kernel config),
> -    load the RDMA transport module:
> +    If the NFS/RDMA server was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
> +    kernel config), load the RDMA transport module:
>  
>      $ modprobe svcrdma
>  
> -    Regardless of how the server was built (module or built-in), start the server:
> +    Regardless of how the server was built (module or built-in), start the
> +    server:
>  
>      $ /etc/init.d/nfs start
>  
> @@ -253,17 +255,17 @@ NFS/RDMA Setup
>  
>    - On the client system
>  
> -    If the NFS/RDMA client was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in kernel config),
> -    load the RDMA client module:
> +    If the NFS/RDMA client was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
> +    kernel config), load the RDMA client module:
>  
>      $ modprobe xprtrdma.ko
>  
> -    Regardless of how the client was built (module or built-in), use this command to
> -    mount the NFS/RDMA server:
> +    Regardless of how the client was built (module or built-in), use this
> +    command to mount the NFS/RDMA server:
>  
>      $ mount -o rdma,port=2050 <IPoIB-server-name-or-address>:/<export> /mnt
>  
> -    To verify that the mount is using RDMA, run "cat /proc/mounts" and check the
> -    "proto" field for the given mount.
> +    To verify that the mount is using RDMA, run "cat /proc/mounts" and check
> +    the "proto" field for the given mount.
>  
>    Congratulations! You're using NFS/RDMA!
> 

  reply	other threads:[~2008-06-02 20:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 19:33 [PATCH] update NFS/RDMA documentation James Lentini
     [not found] ` <alpine.LFD.1.10.0806021530560.26788-5zmYZXM8ymTNoO61VEKW3MYxy48AqY0ZOQ4dku92ua4@public.gmane.org>
2008-06-02 20:02   ` J. Bruce Fields
2008-06-02 20:25     ` James Lentini [this message]
2008-06-02 20:38   ` Chuck Lever
2008-06-02 21:13     ` James Lentini
     [not found]       ` <alpine.LFD.1.10.0806021653360.26788-5zmYZXM8ymTNoO61VEKW3MYxy48AqY0ZOQ4dku92ua4@public.gmane.org>
2008-06-02 22:30         ` Chuck Lever

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=alpine.LFD.1.10.0806021624440.26788@jlentini-linux.nane.netapp.com \
    --to=jlentini@netapp.com \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=talpey@netapp.com \
    --cc=tom@opengridcomputing.com \
    --cc=trond.myklebust@fys.uio.no \
    /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