Hal Rosenstock wrote:
For now, the code will only
abort a send, which should be the more common case. I will need to add
aborting receives later and assume that actual TID collisions would be
extremely rare.
What status code will you use for this ?
I'm returning IB_WC_REM_ABORT_ERR and placing the actual RMPP status code in
the vendor_err field.
The RMPP status does help indicate whether a send or receive is being
aborted, but not in all cases.
What cases are not covered ?
I believe that the following status values are possible for either a send or
receive:
resources exhausted
bad RMPP type
illegal status
unspecified and class specific
- Sean
_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
