@@ -18,6 +18,7 @@ including (but not limited to):
18
18
* Cisco usNIC
19
19
* Cray uGNI
20
20
* Cornelius Networks Omni-Path
21
+ * HPE Slingshot 11
21
22
22
23
In general, the OFI-based components in Open MPI will auto-select
23
24
themselves as appropriate at run time.
@@ -43,8 +44,9 @@ communications:
43
44
``FI_EP_RDM `` endpoints, ``FI_TAGGED `` capabilities, and
44
45
``FI_ORDER_SAS `` ordering).
45
46
46
- #. ``ofi `` BTL: Available since Open MPI v4.0.0, this component is
47
- used for one-sided MPI communications (e.g., ``MPI_PUT ``). The
47
+ #. ``ofi `` BTL: Available since Open MPI v4.0.0, this component is primarily
48
+ intended for one-sided MPI communications (e.g., ``MPI_PUT ``). It
49
+ can also support BTL send/recv operations.
48
50
``ofi `` BTL requires that the Libfabric provider support reliable
49
51
datagrams, RMA and atomic operations, and remote atomic completion
50
52
notifications (specifically: ``FI_EP_RDM `` endpoints, ``FI_RMA ``
@@ -76,6 +78,11 @@ list. For example:
76
78
77
79
shell$ ompi_info --param mtl ofi --level 9
78
80
81
+ .. important :: When using the HPE CXI provider and ``mpirun`` as the job launcher,
82
+ the PRTE ``ras_base_launch_orted_on_hn `` MCA parameter must be set to 1.
83
+ This can be done by adding ``--prtemca ras_base_launch_orted_on_hn 1 `` to the job launch
84
+ command line.
85
+
79
86
For more information refer to the `Libfabric web site
80
87
<https://libfabric.org/> `_.
81
88
0 commit comments