Areas where the majority of clients will need to implement the exact same code make sense to push into the CM. So far there doesn't seem to be any disagreement that the CM has features that it doesn't need. And the list of desired features seem to be:
* Perform QP transitions for the user. * Provide default values when establishing a connection. * Perform retransmissions. * Destroy connection identifiers from/after a callback.
Are there others?
What about: * CM creates the QP when necessary, unless the app provides one. * CM will destroy the QP on connection closure if it owns it.
Frank.
_______________________________________________ openib-general mailing list [EMAIL PROTECTED] http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
