[openib-general] CM header file

[frank zago]

>
> I was trying to match the existing MAD API.  The CM would perform 
> timeouts, but not retries.  Consumers could retry request immediately 
> upon notification of a timeout.  This lets the client change the 
> timeout value.  (I'm negotiable on this, but the cost of having 
> clients initiate retries is basically one function call.)
>
> I have given some thought to how retries should work.  I've thought 
> about adding a new call, ib_retry_cm_send() - or something like that, 
> that resends the last message sent.  Or the callback could indicate to 
> retry.


I have the same problem here than with the handler. A client should be 
able to set timeouts and retries, and let CM take care of the painful stuff.
The complexity should be in the CM, not repeated amongst the clients.

Frank