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

[Tom Duffy]

On Wed, 2005-06-01 at 14:26 -0700, Sean Hefty wrote:
> Talpey, Thomas wrote:
> > Hal's right - it does live in an IB-specific file, though that seems to
> > live in a common directory. I don't think the conversion is sufficiently
> > general to warrant any special status. Isn't it the case that it is
> > Mellanox-hardware specific, not even IB-specific?
> 
> The time format is IB architecture specific.  The CM is exposing a field 
> value defined by the spec.  If a different format would be a better 
> alternative, we can look at changing it.

I was looking at some of the ULPs.  SDP sets the timeout to 20, without
explanation.  DAPL has a #define (set to 20 saying it is 4 sec in a
comment).  simple example?  Set to 20, no reason.  To me, it ends up
just being this opaque value.  Maybe some pre#defines in CM would make
it clearer.  Unfortunately, advertising milliseconds or jiffies will
just confuse consumers since the timeout cannot be that granular.

-tduffy
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.openfabrics.org/pipermail/general/attachments/20050601/22d12706/attachment.sig>