@@ -18,6 +18,7 @@ including (but not limited to):
1818* Cisco usNIC
1919* Cray uGNI
2020* Cornelius Networks Omni-Path
21+ * HPE Slingshot 11
2122
2223In general, the OFI-based components in Open MPI will auto-select
2324themselves as appropriate at run time.
@@ -43,8 +44,9 @@ communications:
4344 ``FI_EP_RDM `` endpoints, ``FI_TAGGED `` capabilities, and
4445 ``FI_ORDER_SAS `` ordering).
4546
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.
4850 ``ofi `` BTL requires that the Libfabric provider support reliable
4951 datagrams, RMA and atomic operations, and remote atomic completion
5052 notifications (specifically: ``FI_EP_RDM `` endpoints, ``FI_RMA ``
@@ -76,6 +78,11 @@ list. For example:
7678
7779 shell$ ompi_info --param mtl ofi --level 9
7880
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+
7986For more information refer to the `Libfabric web site
8087<https://libfabric.org/> `_.
8188
0 commit comments