[Pkg-ofed-commits] [libfabric] 108/123: Updated nroff-generated man pages

Ana Beatriz Guerrero López ana at moszumanska.debian.org
Sat Oct 22 12:28:35 UTC 2016


This is an automated email from the git hooks/post-receive script.

ana pushed a commit to annotated tag v1.1.1
in repository libfabric.

commit a446bbb1371420640ef91f9fd3e04fdc9760d0b3
Author: OFIWG Bot <ofiwg at lists.openfabrics.org>
Date:   Mon Sep 28 16:21:07 2015 -0700

    Updated nroff-generated man pages
---
 man/man7/fi_usnic.7 | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/man/man7/fi_usnic.7 b/man/man7/fi_usnic.7
index 7ea92ae..7b9efb5 100644
--- a/man/man7/fi_usnic.7
+++ b/man/man7/fi_usnic.7
@@ -1,4 +1,4 @@
-.TH fi_usnic 7 "2015\-07\-31" "Libfabric Programmer\[aq]s Manual" "\@VERSION\@"
+.TH fi_usnic 7 "2015\-09\-28" "Libfabric Programmer\[aq]s Manual" "\@VERSION\@"
 .SH NAME
 .PP
 The usNIC Fabric Provider
@@ -13,6 +13,7 @@ networks.
 .IP \[bu] 2
 The \f[I]usnic\f[] libfabric provider requires the use of the "libnl"
 library.
+.RS 2
 .IP \[bu] 2
 There are two versions of libnl generally available: v1 and v3; the
 usnic provider can use either version.
@@ -27,6 +28,7 @@ If you have libnl (either v1 or v3) installed in a non-standard location
 libfabric\[aq]s configure where to find libnl via the
 \f[C]--with-libnl=DIR\f[] command line option (where DIR is the
 installation prefix of the libnl package).
+.RE
 .IP \[bu] 2
 The most common way to use the libfabric usnic provider is via an MPI
 implementation that uses libfabric (and the usnic provider) as a lower
@@ -36,6 +38,7 @@ in this use case -- the MPI implementation hides all these details from
 the application.
 .IP \[bu] 2
 If you are writing applications directly to the libfabric API:
+.RS 2
 .IP \[bu] 2
 \f[I]FI_EP_DGRAM\f[] endpoints are the best supported method of
 utilizing the usNIC interface.
@@ -48,9 +51,6 @@ are only lightly tested.
 It is likely that there are still some bugs in these endpoint types.
 RMA is not yet supported.
 .IP \[bu] 2
-\f[I]FI_EP_RDM\f[] support is not 100% robust and occasionally leads to
-hangs in the \f[C]fi_rdm_pingpong\f[] test from fabtests.
-.IP \[bu] 2
 \f[C]fi_provider\f[](7) lists requirements for all providers.
 The following limitations exist in the \f[I]usnic\f[] provider:
 .RS 2
@@ -65,7 +65,10 @@ Passive endpoints only support listen, setname, and getname CM
 operations.
 .IP \[bu] 2
 \f[I]FI_EP_DGRAM\f[] endpoints support \f[C]fi_sendmsg()\f[] and
-\f[C]fi_recvmsg()\f[], but all flags are ignored.
+\f[C]fi_recvmsg()\f[], but some flags are ignored.
+\f[C]fi_sendmsg()\f[] supports \f[C]FI_INJECT\f[] and
+\f[C]FI_COMPLETION\f[].
+\f[C]fi_recvmsg()\f[] supports \f[C]FI_MORE\f[].
 .IP \[bu] 2
 Address vectors only support \f[C]FI_AV_MAP\f[].
 .IP \[bu] 2
@@ -74,12 +77,13 @@ No counters are supported.
 The tag matching interface is not supported.
 .IP \[bu] 2
 \f[I]FI_MSG_PREFIX\f[] is only supported on \f[I]FI_EP_DGRAM\f[] and
-usage is limited to the 1.1 release.
+usage is limited to releases 1.1 and beyond.
 .RE
 .IP \[bu] 2
 The usnic libfabric provider supports extensions that provide
 information and functionality beyond the standard libfabric interface.
 See the "USNIC EXTENSIONS" section, below.
+.RE
 .SH USNIC EXTENSIONS
 .PP
 The usnic libfabric provider exports extensions for additional VIC,

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-ofed/libfabric.git



More information about the Pkg-ofed-commits mailing list