Olaf Kirch wrote:
Okay, there's a third way to fix this, which may even work with today's Oracle
IPC code. The hack is to not submit the fastreg WR until we post a SEND that
transmits the rkey to a peer. Then
- we have a QP to post the WRs to
- we post the fastreg and the SEND to the same QP,
ensuring that the peer doesn't initiate the RDMA
before we've set up the memory registration.
Yes, as Steve noted, using the same QP for the fastreg and send that
carries the rkey/stag is a must since the send should be fenced on the
fastreg completion to make sure the remote side uses a valid key.
Or.
_______________________________________________
general mailing list
[email protected]
http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
