rdma: removed SAS ordering requirement

There is no case in which not having Send-After-Send ordering causes issues, so it is safe to remove it. The only possible reordering that can happen is if a ctrl message is received before a connect response message, but we already deal with this case correctly, since the control message is added to the msgbuf and retrieved when isend is called. Signed-off-by: Amedeo Sapio <[email protected]>
aws · Mar 22, 2024 · b4e1ec6 · b4e1ec6
1 parent 15d0adf
commit b4e1ec6
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/src/nccl_ofi_rdma.c b/src/nccl_ofi_rdma.c
@@ -5743,8 +5743,8 @@ static void get_hints(struct fi_info *hints)
 
 	hints->mode = 0;
 
-	hints->tx_attr->msg_order = FI_ORDER_SAS;
-	hints->rx_attr->msg_order = FI_ORDER_SAS;
+	hints->tx_attr->msg_order = FI_ORDER_NONE;
+	hints->rx_attr->msg_order = FI_ORDER_NONE;
 
 	hints->ep_attr->type = FI_EP_RDM;