diff options
| author | Raghavendra G <rgowdapp@redhat.com> | 2014-05-28 21:56:02 +0530 |
|---|---|---|
| committer | Vijay Bellur <vbellur@redhat.com> | 2014-05-29 23:32:00 -0700 |
| commit | 8049696c48dc1a51a76629c2bd2fdc1cf187a5b5 (patch) | |
| tree | 76fea2df8052136e903a0a178628e0dad0f5c32f | |
| parent | 42332a4269359a9c2dcb66a8abbc75a649f767a0 (diff) | |
doc/rdmacm: fix formatting errors.
BUG: 1086743
Change-Id: I24798ef1e359dc2508d495e244151e93537b52a4
Signed-off-by: Raghavendra G <rgowdapp@redhat.com>
Reviewed-on: http://review.gluster.org/7914
Reviewed-by: Humble Devassy Chirammal <humble.devassy@gmail.com>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
Tested-by: Vijay Bellur <vbellur@redhat.com>
| -rw-r--r-- | doc/features/rdmacm.md | 34 |
1 files changed, 17 insertions, 17 deletions
diff --git a/doc/features/rdmacm.md b/doc/features/rdmacm.md index b4c06ea2172..caacab40452 100644 --- a/doc/features/rdmacm.md +++ b/doc/features/rdmacm.md @@ -1,17 +1,17 @@ -## Rdma Connection manager ## - -### What? ### -Infiniband requires addresses of end points to be exchanged using an out-of-band channel (like tcp/ip). Glusterfs used a custom protocol over a tcp/ip channel to exchange this address. However, librdmacm provides the same functionality with the advantage of being a standard protocol. This helps if we want to communicate with a non-glusterfs entity (say nfs client with gluster nfs server) over infiniband. - -### Dependencies ### -* [IP over Infiniband](http://pkg-ofed.alioth.debian.org/howto/infiniband-howto-5.html) - The value to *option* **remote-host** in glusterfs transport configuration should be an IPoIB address -* [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) - -### 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). - -### External links ### -* [Infiniband Howto](http://pkg-ofed.alioth.debian.org/howto/infiniband-howto.html) +## Rdma Connection manager ##
+
+### What? ###
+Infiniband requires addresses of end points to be exchanged using an out-of-band channel (like tcp/ip). Glusterfs used a custom protocol over a tcp/ip channel to exchange this address. However, librdmacm provides the same functionality with the advantage of being a standard protocol. This helps if we want to communicate with a non-glusterfs entity (say nfs client with gluster nfs server) over infiniband.
+
+### Dependencies ###
+* [IP over Infiniband](http://pkg-ofed.alioth.debian.org/howto/infiniband-howto-5.html) - The value to *option* **remote-host** in glusterfs transport configuration should be an IPoIB address
+* [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)
+
+### 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).
+
+### External links ###
+* [Infiniband Howto](http://pkg-ofed.alioth.debian.org/howto/infiniband-howto.html)
|