>We could solve this by implementing a process running on the same node as the >SA. >And it's probably not too hard to add a way for opensm to spit out >the table into an external file when it gets a signal or something.
I agree that there are ways to solve this, but those solutions won't work with existing SAs and define a new SA interface. If we're willing to break compatibility or add extensions, we could also extend the SA to provide better support for caching. For example, add a new 'path updated' trap. IMO, I don't think that there's a huge issue initially populating the cache. The problems all seem to fall into keeping it updated. I originally thought this would have been a bigger deal, but given that ipoib doesn't update its cache, it doesn't seem to be an issue in practice. - Sean _______________________________________________ general mailing list general@lists.openfabrics.org http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
