On Wednesday 22 June 2011 19:14, Hefty, Sean wrote:

This is partly true, and I haven't come up with a better way to handle this.  
Note that the patches allow the original creator of the TGT QP to destroy it by simply calling ibv_destroy_qp().
This doesn't handle the process dying, but maybe that's not a real concern.  

Correct, that was not the MPI community's main concern.
 

After looking at the implementation more, what I didn't like about the reg/unreg
calls is that it is independent of receiving data on an SRQ.  That is, a user can
receive data on an SRQ through a TGT QP before they have registered and after unregistering.

That is correct, but the registering/unregistering is for expressing "interest" in the TGT QP, only (i.e., for
reference counting only, as you indicated), and not at all for enabling the SRQ to receive traffic.
When the reference count on the TGT QP goes to zero, it is automatically destroyed.
(The TGT QP creator itself takes a reference, which is decremented when either the
process exits, or it calls the deref procedure.)

In my thread post
    http://lists.openfabrics.org/pipermail/general/2008-January/045302.html  ,
I describe the intended workflow for this interface.

-Jack

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html