shaharf> Regarding the content of the ping packet, I encountered
shaharf> many ideas in the list, most of them good and valid. My
shaharf> opinion is that the kernel server should reply only on
shaharf> the most basic "ping queries" and any further ping
shaharf> enhancements (for example, returning gid + lid, etc.)
shaharf> should be implemented in a separate, probably user mode
shaharf> server. This will be the most flexible solution and will
shaharf> reduce the kernel pollution. In fact I started to
shaharf> implement a (usermode only) "ibsystat service" that will
shaharf> supply such extensions. Currently, what I have in mind is
shaharf> to provide basic host information: number of CPUs,
shaharf> memory, utilization, etc., IB information: number of
shaharf> hcas, models, etc. The idea is to ease some cluster wide
shaharf> operations common in large cluster setup. Any ideas and
shaharf> suggestions are welcomes.
It doesn't seems like a good idea to reinvent cluster management in an
IB-specific way. I would rather see this sort of thing built on top
of an existing tool like Ganglia (http://ganglia.sf.net).
- R.
_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
