Hal Rosenstock wrote: > On Sun, 2008-05-18 at 15:36 +0300, Moni Shoua wrote: >> The purpose of this patch is to make the events that are related to SM change >> (namely CLIENT_REREGISTER event and SM_CHANGE event) less disruptive. >> When SM related events are handled, it is not necessary to flush unicast >> info from device but only multicast info. > > How is unicast invalidation handled on these changes ? On a local LID > change event, how does an end port know/determine what else (e.g. other > LIDs, paths) the SM might have changed (that specifically might affect > IPoIB since this is limited to IPoIB) ? I'm not sure I understand the question but local LID change would be handled as before with a LID_CHANGE event. For this type of event, there is not change in what IPoIB does to cope.
> > Also, wouldn't there be similar issues with other ULPs ? There might be but the purpose of this one is to make things better for IPoIB > > -- Hal > _______________________________________________ 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
