Moni Shoua wrote: > The patch tries to solve the problem of device going down and paths being > flushed on SM change event. The method is to mark the paths as candidates for > refresh (with a valid flag) and wait for ARP probe to start a flow of path > lookup that leads to patch query which ends up in path (and address handle) > refresh. > The solution requires a different and less intrusive handling of SM change > event. For that, the second argument of the flush function changed it's > meaning > from boolean flag to a level. > In most cases, SM failover doesn't cause LID change so traffic won't stop. In > the rare cases of LID change, the remote host (the one that hadn't changed > its LID) will lose connectivity until paths are refreshed. This is no worse > than > the current state. In fact, preventing the device from going down saves > packets > that otherwise would be lost. > > Signed-off-by: Moni Levy <[EMAIL PROTECTED]> > Signed-off-by: Moni Shoua <[EMAIL PROTECTED]> > ---
Hi Roland, This issue is important to us. I'd appreciate if you review it and make an opinion. I understand it's kind of late now to make it to 2.6.26 but we hope to have it in 2.6.27 thanks MoniS _______________________________________________ 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
