Michael Krause wrote:
accordingly. I can envision how to construct such a knowledge that is interconnect independent but it requires more "standardization" about what defines the QoS requirements - latency, bandwidth, service rate, no single point of failure, etc. What I see so far does not address these issues.
I removed the QoS structures from my latest version until something can be defined that is usable, and it's clear how the QoS requirements map to the underlying routes. (My personal experience with QoS parameters in an API is that it never moves beyond the stage of being a place-holder.) Any patch that defines and implements QoS to routing would be greatly appreciated. And reference to an application that makes use of it would be helpful.
- Sean _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
