>yes.when the client rebooted and failed to connect the server, the >event.status is >'IB_CM_REJ_STALE_CONN' . On the client ,when I created a QP using the old >rdma_cm_id which failed in the first connection to retry connection to server, >the call to function rdma_create_qp() returned -22(-EINVAL) all the time.
This is expected. The rdma_cm_id can only be used for a single connection. The underlying state machine does not reset. >My question: Are there some methods that the server can be notifed when it lose >the connection such as the client's reboot?So the server can destroy the >rdma_cm_id and pass the stale connection check. The client needs no retry for >new rdma_cm_id after reboot. If the server isn't using the connections, then they could stay around. I don't know how you can avoid this for a general case short of keep-alive messages. For actual stale connections, it would require a kernel change, but the kernel detects this and _could_ force a disconnect on the local side. - Sean -- 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
