diff options
| author | Humble Chirammal <hchiramm@redhat.com> | 2014-09-23 23:05:16 +0530 |
|---|---|---|
| committer | Vijay Bellur <vbellur@redhat.com> | 2014-11-26 00:17:59 -0800 |
| commit | 6c5b74c66cc0eb10edf5e4d3a726c7efddb5842c (patch) | |
| tree | 06d3695f6a0657d1808c3bcf4d052272ebad8723 /doc | |
| parent | 7f7dabd7d0df82678e2977002b3d1068ae283dce (diff) | |
doc: Avoid duplicate rdma notes.
Change-Id: I5ede0ffad3870d8d86cb5d551ce188c649b04b44
Signed-off-by: Humble Chirammal <hchiramm@redhat.com>
Reviewed-on: http://review.gluster.org/8826
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/features/rdma-cm-in-3.4.0.txt | 9 | ||||
| -rw-r--r-- | doc/features/rdmacm.md | 9 |
2 files changed, 9 insertions, 9 deletions
diff --git a/doc/features/rdma-cm-in-3.4.0.txt b/doc/features/rdma-cm-in-3.4.0.txt deleted file mode 100644 index fd953e56b3f..00000000000 --- a/doc/features/rdma-cm-in-3.4.0.txt +++ /dev/null @@ -1,9 +0,0 @@ -Following is the impact of http://review.gluster.org/#change,149. - -New userspace packages needed: -librdmacm -librdmacm-devel - -rdmacm needs an IPoIB address for connection establishment. This requirement results in following issues: -* Because of bug #890502, we've to probe the peer on an IPoIB address. This imposes a restriction that all volumes created in the future have to communicate over IPoIB address (irrespective of whether they use gluster's tcp or rdma transport). -* Currently client has an independence to choose b/w tcp and rdma transports while communicating with the server (by creating volumes with transport-type tcp,rdma). This independence was a byproduct of our ability use the normal channel used with transport-type tcp for rdma connectiion establishment handshake too. However, with new requirement of IPoIB address for connection establishment, we loose this independence (till we bring in multi-network support - where a brick can be identified by a set of ip-addresses and we can choose different pairs of ip-addresses for communication based on our requirements - in glusterd). diff --git a/doc/features/rdmacm.md b/doc/features/rdmacm.md index caacab40452..2c287e85fb6 100644 --- a/doc/features/rdmacm.md +++ b/doc/features/rdmacm.md @@ -8,7 +8,16 @@ Infiniband requires addresses of end points to be exchanged using an out-of-band * [rdma cm kernel module](http://pkg-ofed.alioth.debian.org/howto/infiniband-howto-4.html#ss4.4)
* [user space rdmacm library - librdmacm](https://www.openfabrics.org/downloads/rdmacm)
+### rdma-cm in >= GlusterFs 3.4 ###
+
+Following is the impact of http://review.gluster.org/#change,149.
+
+New userspace packages needed:
+librdmacm
+librdmacm-devel
+
### Limitations ###
+
* Because of bug [890502](https://bugzilla.redhat.com/show_bug.cgi?id=890502), we've to probe the peer on an IPoIB address. This imposes a restriction that all volumes created in the future have to communicate over IPoIB address (irrespective of whether they use gluster's tcp or rdma transport).
* Currently client has independence to choose b/w tcp and rdma transports while communicating with the server (by creating volumes with **transport-type tcp,rdma**). This independence was a by-product of our ability to use the tcp/ip channel - transports with *option transport-type tcp* - for rdma connection establishment handshake too. However, with new requirement of IPoIB address for connection establishment, we loose this independence (till we bring in [multi-network support](https://bugzilla.redhat.com/show_bug.cgi?id=765437) - where a brick can be identified by a set of ip-addresses and we can choose different pairs of ip-addresses for communication based on our requirements - in glusterd).
|