From bfae8ea8288dc55cce0f7fc43c1f4b329ae1100b Mon Sep 17 00:00:00 2001 From: Jeff Squyres Date: Wed, 7 May 2008 16:53:05 +0000 Subject: [PATCH] The comment wasn't long enough; I felt the need to make it longer (and explain a little more ;-) ). This commit was SVN r18404. --- ompi/mca/btl/openib/btl_openib_component.c | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) diff --git a/ompi/mca/btl/openib/btl_openib_component.c b/ompi/mca/btl/openib/btl_openib_component.c index 3e5876b2aa..f32798f033 100644 --- a/ompi/mca/btl/openib/btl_openib_component.c +++ b/ompi/mca/btl/openib/btl_openib_component.c @@ -2068,11 +2068,14 @@ error: if(endpoint && endpoint->endpoint_proc && endpoint->endpoint_proc->proc_ompi) remote_proc = endpoint->endpoint_proc->proc_ompi; - /* For iWARP, the TCP connection is tied to the QP once the QP is in RTS. - * And destroying the QP is thus tied to connection teardown for iWARP. - * To destroy the connection in iWARP you must move the QP out of RTS, either - * into CLOSING for a nice graceful close, or to ERROR if you want to be rude. - * In both cases, all pending non-completed SQ and RQ WRs must be flushed. + /* For iWARP, the TCP connection is tied to the QP once the QP is + * in RTS. And destroying the QP is thus tied to connection + * teardown for iWARP. To destroy the connection in iWARP you + * must move the QP out of RTS, either into CLOSING for a nice + * graceful close (e.g., via rdma_disconnect()), or to ERROR if + * you want to be rude (e.g., just destroying the QP without + * disconnecting first). In both cases, all pending non-completed + * SQ and RQ WRs will automatically be flushed. */ if (wc->status == IBV_WC_WR_FLUSH_ERR && IBV_TRANSPORT_IWARP == hca->ib_dev->transport_type) { return;