From: Michael Wang <yun.wang@profitbricks.com>
To: Roland Dreier <roland@kernel.org>,
Sean Hefty <sean.hefty@intel.com>,
Hal Rosenstock <hal@dev.mellanox.co.il>,
Doug Ledford <dledford@redhat.com>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Cc: Michael Wang <yun.wang@profitbricks.com>,
Or Gerlitz <ogerlitz@mellanox.com>,
Ira Weiny <ira.weiny@intel.com>,
Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Subject: [PATCH RFC] Documentation/infiniband: Add docs for rdma-helpers
Date: Wed, 13 May 2015 15:24:32 +0200 [thread overview]
Message-ID: <1431523472-10888-1-git-send-email-yun.wang@profitbricks.com> (raw)
This is the following patch for:
https://lkml.org/lkml/2015/5/5/417
which try to document the settled rdma_cap_XX().
Highlights:
There could be many missing/mistakes/misunderstanding, please don't
be hesitate to point out the issues, any suggestions to improve or
complete the description are very welcomed ;-)
Signed-off-by: Michael Wang <yun.wang@profitbricks.com>
---
Documentation/infiniband/rdma_helpers.txt | 76 +++++++++++++++++++++++++++++++
1 file changed, 76 insertions(+)
create mode 100644 Documentation/infiniband/rdma_helpers.txt
diff --git a/Documentation/infiniband/rdma_helpers.txt b/Documentation/infiniband/rdma_helpers.txt
new file mode 100644
index 0000000..abc75ec
--- /dev/null
+++ b/Documentation/infiniband/rdma_helpers.txt
@@ -0,0 +1,76 @@
+RDMA HELPERS
+
+ For core layer, below helpers are used to check if a paticular capability
+ is supported by the port.
+
+ rdma_cap_ib_mad - Infiniband Management Datagrams.
+ rdma_cap_ib_smi - Infiniband Subnet Management Interface.
+ rdma_cap_ib_cm - Infiniband Communication Manager.
+ rdma_cap_iw_cm - IWARP Communication Manager.
+ rdma_cap_ib_sa - Infiniband Subnet Administration.
+ rdma_cap_ib_mcast - Infiniband Multicast.
+ rdma_cap_read_multi_sge - RDMA Read Multiple Scatter-Gather Entries.
+ rdma_cap_af_ib - Native Infiniband Address.
+ rdma_cap_eth_ah - Ethernet Address Handler.
+
+USAGE
+
+ if (rdma_cap_XX(device, i)) {
+ /* The port i of device support XX */
+ ...
+ } else {
+ /* The port i of device don't support XX */
+ ...
+ }
+
+ rdma_cap_ib_mad
+ ---------------
+ Management Datagrams (MAD) is the prototype of management packet
+ to be used by all the kinds of infiniband managers, use the helper
+ to verify the port before utilize related features.
+
+ rdma_cap_ib_smi
+ ---------------
+ Subnet Management Interface (SMI) will handle SMP packet from SM
+ in an infiniband fabric, use the helper to verify the port before
+ utilize related features.
+
+ rdma_cap_ib_cm
+ ---------------
+ Communication Manager (CM) will handle the connections between
+ adaptors, currently there are two different implementation,
+ IB or IWARP, use the helper to verify whether the port using
+ IB-CM or not
+
+ rdma_cap_iw_cm
+ ---------------
+ IWARP has it's own implemented CM which is different from infiniband,
+ use the helper to check whether the port using IWARP-CM or not.
+
+ rdma_cap_ib_sa
+ ---------------
+ Subnet Administration (SA) is the database built by SM in an
+ infiniband fabric, use the helper to verify the port before
+ utilize related features.
+
+ rdma_cap_ib_mcast
+ ---------------
+ Multicast is the feature for one QP to send messages to multiple
+ QP in an infiniband fabric, use the helper to verify the port before
+ utilize related features.
+
+ rdma_cap_read_multi_sge
+ ---------------
+ RDMA read operation could support multiple scatter-gather entries,
+ use the helper to verify wthether the port support this feature
+ or not.
+
+ rdma_cap_af_ib
+ ---------------
+ RDMA address format could be ethernet or infiniband, use the helper
+ to verify whether the port support infiniband format or not.
+
+ rdma_cap_eth_ah
+ ---------------
+ Infiniband address handler format is special in ethernet fabric, use
+ the helper to verify whether the port is using ethernet format or not.
--
2.1.0
next reply other threads:[~2015-05-13 13:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 13:24 Michael Wang [this message]
[not found] ` <1431523472-10888-1-git-send-email-yun.wang-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2015-05-13 15:11 ` [PATCH RFC] Documentation/infiniband: Add docs for rdma-helpers Doug Ledford
2015-05-13 16:42 ` Hefty, Sean
2015-05-15 8:31 ` Michael Wang
[not found] ` <5555AEE5.9060503-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2015-05-15 14:40 ` Doug Ledford
[not found] ` <1431700819.27722.15.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-15 15:02 ` Michael Wang
[not found] ` <1431529914.2377.22.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-15 8:12 ` Michael Wang
[not found] ` <5555AA7D.7080503-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2015-05-15 14:27 ` Doug Ledford
[not found] ` <1431700060.27722.7.camel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2015-05-15 14:38 ` Michael Wang
2015-05-13 15:59 ` Jason Gunthorpe
2015-05-15 7:51 ` Michael Wang
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=1431523472-10888-1-git-send-email-yun.wang@profitbricks.com \
--to=yun.wang@profitbricks.com \
--cc=dledford@redhat.com \
--cc=hal@dev.mellanox.co.il \
--cc=ira.weiny@intel.com \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=roland@kernel.org \
--cc=sean.hefty@intel.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