> As previously stated, IBM HCA will address these issues. However, > my understanding is that mthca/Topspin adapters also have a problem > (too high a value for the Local CA Delay Ack). Both HCAs need to be > fixed for good interoperability.
I think you're misunderstanding what local CA ack delay means. This is a property of an HCA that is not (necessarily) subject to tuning -- it is just a property of the HCA, namely the maximum amount of time it may take to generate an ACK. So if a certain HCA reports a value of 15, then that means that any remote HCA talking to it must be prepared for a delay of 4.096 * 2^15 usecs before receiving an ACK. If the ACK delays on both sides are not being taken into account properly when establishing a connection, then I guess that is a bug in our CM. - R. _______________________________________________ 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
