Quoting r. Sean Hefty <[EMAIL PROTECTED]>: > Subject: [PATCH 0/4] Dispatch communication related events to the IB CM > > The following set of patches forwards communication related events to the IB > CM > for processing. Communication events of interest are communication > established > and path migration, with only the former is currently handled by the IB CM. > > This removes the need for users to trap for these events and pass the > information onto IB CM. Communication established events can be handled by > the > ib_cm_establish() routine, but no mechanism exists to notify the IB CM of path > migration. This adds the framework for doing so. > > Signed-off-by: Sean Hefty <[EMAIL PROTECTED]> >
Some things unclear to me: 1. Is a user somehow *required* to call ib_cm_establish if he gets the event? E.g. what about cma users? 2. There are now two ways CM gets notified about Communication established events - what happends if both the user calls ib_cm_establish, and CM gets this directly? 3. If I understand it correctly, CM does not yet know how to switch to the alternate path for CM messages. So, is the patch still useful by itself, or is it more of a framework preparatory work? -- MST _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
