The SQD state is mapped to the iWARP CLOSING state. In this state, the
protocol tries to do an orderly connection shutdown. In TCP terms, it
will do the TCP FIN, FIN/ACK, ACK orderly shutdown. If that fails, or
for other reasons, the provider (or the application) might just move the
QP to ERR which maps to the iWARP ERROR state which would cause an
abrupt connection reset (one side or both sends a TCP RST).
On 10/30/2013 4:48 PM, Hefty, Sean wrote:
Can one of the iwarp developers tell me why the QP transition for iwarp is SQD
rather than ERR during rdma_disconnect? I can't remember the reason, and I
don't see that SQD is listed as a QP state in the iwarp spec.
int rdma_disconnect(struct rdma_cm_id *id)
{
...
switch (id->verbs->device->transport_type) {
case IBV_TRANSPORT_IB:
ret = ucma_modify_qp_err(id);
break;
case IBV_TRANSPORT_IWARP:
ret = ucma_modify_qp_sqd(id);
break;
- 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
--
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
