On Fri, 2007-04-13 at 00:55, Hefty, Sean wrote: > >When the node is diagnosed and disconnected, SM will bring the rate > back up. > > But how? Doesn't it require re-registration of all multicast groups and > clients registered for SA events? > > >As I said, there are tens of ways a bad node can hurt performance, > >and we don't/can't handle them. Why focus on ipoib? It's > >the only way to connect to node on some fabrics, it > >really must be up at all times. > > But the solution is affecting all multicast traffic, not just that > related to ipoib. If you want all nodes to be able to join the ipoib > multicast group, why not just create the group at the lower rate?
Exactly. 1x SDR could be the admin choice. That was not chosen as the default so as not to mask performance issues. > ipoib > multicast performance doesn't seem that critical. It's not just IPoIB multicast; it's anything that uses the IPv4 broadcast group. > Whereas disrupting > other multicast groups, which could actively be in use by MPI, may be. Also, it disrupts all multicast groups whether or not they are affected by this node. -- Hal > - Sean > _______________________________________________ > 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 _______________________________________________ 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
