[openib-general] [PATCHv2][RFC] kDAPL: use cm timers instead of own

[James Lentini]

That would be another way to interpret this: that each time the CM 
times out, DAPL should re-attempt to establish a connection. However, 
the original implementation didn't do this and the feedback I've 
received is that such a feature would not be appropriate for the 
kernel. 

If there are kernel applications that want this, we can add it.

On Wed, 8 Jun 2005, Tom Duffy wrote:

tduffy> On Wed, 2005-06-08 at 11:44 -0400, James Lentini wrote:
tduffy> > We interpreted the above to mean "give the connection protocol as 
tduffy> > much time as it needs to establish a connection, but don't mask 
tduffy> > errors (no path to the remove node, etc.)". For that reason we changed 
tduffy> > the variable name to DAT_TIMEOUT_MAX.
tduffy> 
tduffy> Well, let's say the end node is not there yet.  Should the CM keep
tduffy> trying indefinitely waiting for somebody to show up and respond?
tduffy> 
tduffy> -tduffy
tduffy>