From: Leon Romanovsky <leon@leon.nu>
To: Shirley Ma <shirley.ma@oracle.com>
Cc: Anna Schumaker <Anna.Schumaker@netapp.com>,
Trond Myklebust <trond.myklebust@primarydata.com>,
Chuck Lever <Chuck.Lever@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-rdma <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH V2] nfs: add mount proto=rdma6 option for NFS/RDMA IPv6 addressing
Date: Mon, 4 Apr 2016 22:50:20 +0300 [thread overview]
Message-ID: <20160404195020.GH5264@leon.nu> (raw)
In-Reply-To: <5702AF3F.90500@oracle.com>
On Mon, Apr 04, 2016 at 11:15:27AM -0700, Shirley Ma wrote:
> RFC 5666: The "rdma" netid is to be used when IPv4 addressing
> is employed by the underlying transport, and "rdma6" for IPv6
> addressing.
> Add mount -o proto=rdma6 option to support NFS/RDMA IPv6 addressing.
>
> Changes from v1:
> - Integrated comments from Chuck Level, Anna Schumaker, Trodt Myklebust
> - Add a little more to the patch description to describe NFS/RDMA
> IPv6 usage
> - Removed duplicated rdma6 define
> - Removed Opt_xprt_rdma mountfamily since this doesn't support
>
> Signed-off-by: Shirley Ma <shirley.ma@oracle.com>
It will be great if you can update the Documentation too.
Thanks
next prev parent reply other threads:[~2016-04-04 19:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 18:30 [PATCH] nfs: add nfs IPv6 rdma6 mount option support Shirley Ma
2016-03-16 18:46 ` J. Bruce Fields
2016-03-22 19:38 ` Anna Schumaker
2016-03-22 21:24 ` Chuck Lever
2016-03-22 21:46 ` Trond Myklebust
2016-03-22 21:52 ` Chuck Lever
2016-03-22 21:55 ` Trond Myklebust
2016-03-22 22:01 ` Chuck Lever
2016-03-23 18:03 ` Shirley Ma
2016-04-04 18:15 ` [PATCH V2] nfs: add mount proto=rdma6 option for NFS/RDMA IPv6 addressing Shirley Ma
2016-04-04 19:50 ` Leon Romanovsky [this message]
2016-04-04 20:23 ` Shirley Ma
2016-04-04 22:08 ` [PATCH] Documentation nfs-rdma.txt: Update nfs-rdma kernel module name and add IPv6 addressing option rdma6 Shirley Ma
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=20160404195020.GH5264@leon.nu \
--to=leon@leon.nu \
--cc=Anna.Schumaker@netapp.com \
--cc=Chuck.Lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=shirley.ma@oracle.com \
--cc=trond.myklebust@primarydata.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 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).