public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: James Lentini <jlentini@netapp.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] NFS/RDMA documentation update
Date: Thu, 8 Jan 2009 15:22:41 -0500	[thread overview]
Message-ID: <20090108202241.GC19312@fieldses.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0901081309060.3209@jlentini-linux.nane.netapp.com>

On Thu, Jan 08, 2009 at 01:13:26PM -0500, James Lentini wrote:
> 
> Bruce,
> 
> Please consider this patch for 2.6.29:
> 
> Update the NFS/RDMA documentation to use the new port number assigned 
> by IANA.

Applied, thanks!--b.

> 
> Signed-off-by: James Lentini <jlentini@netapp.com>
> ---
> 
>  nfs-rdma.txt |    4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> --- a/Documentation/filesystems/nfs-rdma.txt	2008-12-24 18:26:37.000000000 -0500
> +++ b/Documentation/filesystems/nfs-rdma.txt	2009-01-08 09:52:32.193769000 -0500
> @@ -251,7 +251,7 @@
>  
>      Instruct the server to listen on the RDMA transport:
>  
> -    $ echo rdma 2050 > /proc/fs/nfsd/portlist
> +    $ echo rdma 20049 > /proc/fs/nfsd/portlist
>  
>    - On the client system
>  
> @@ -263,7 +263,7 @@
>      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
> +    $ mount -o rdma,port=20049 <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.

      reply	other threads:[~2009-01-08 20:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 18:13 [PATCH] NFS/RDMA documentation update James Lentini
2009-01-08 20:22 ` J. Bruce Fields [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=20090108202241.GC19312@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=jlentini@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --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