Roland Dreier wrote:
Sean> I'm not sure that peer-to-peer needs to be exposed by the Sean> API. The CM should be able to determine the connection Sean> model when matching a received MAD with a local service ID. Sean> I.e. does the local service ID match with a listen request Sean> or a connection request...
Nope, a consumer has to say whether an active connection request is peer-to-peer or not. It's entirely possible for two systems to be listening for the same service, and want to make two connections (ie the normal TCP-like case where system A connects to port X on system B at the same time as system B connects to the same port X on system A). Or the application may want peer-to-peer semantics. There's no way for the CM to know without being told.
My thinking was that the connection model isn't carried in the CM MADs however, so a receiving CM has to determine how to match the connection request based on what the remote user requested, which isn't known.
I guess that by not having this parameter, an incoming request could be matched incorrectly with an outgoing request, if the local listening service isn't up. I'll add a peer_to_peer parameter to ib_cm_req_param.
- Sean _______________________________________________ openib-general mailing list [EMAIL PROTECTED] http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
