Applications based on the rdma-cm may assume that established event is always delivered by the the kernel stack, clarify that.
Signed-off-by: Or Gerlitz <[email protected]> diff --git a/man/rdma_notify.3 b/man/rdma_notify.3 index 7114ac4..82e1008 100644 --- a/man/rdma_notify.3 +++ b/man/rdma_notify.3 @@ -24,6 +24,8 @@ necessary, however if connection establishment is done out of band QP that is not yet considered connected. This routine forces the connection into an established state in this case in order to handle the rare situation where the connection never forms on its own. +Calling this routine ensures the delivery of the RDMA_CM_EVENT_ESTABLISHED +event to the application. Events that should be reported to the CM are: IB_EVENT_COMM_EST. .SH "SEE ALSO" rdma_connect(3), rdma_accept(3), rdma_listen(3) -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
