> 1. Remove ibstat and use ibv_devinfo instead > 2. Change ibstat to obtain the fdr10 information using ibverbs > 3. Move the is_fdr10 functionality into OS specific files or code > sections of ibstat > 4. Change ibstat to obtain fdr10 data using MADs or some other OS > independent mechanism > 5. Change ibumad so that it provides the fdr10 data > Note: umad has OS dependent implementation anyway, but the windows > umad would > depend on the data being available from ibverbs > 6. ??? > > Can someone explain why the information can't come from the > umad_port::rate field? > > > Because fdr10 is non standard, there's no rate for this; it overloads QDR > based rates as both are 10 Gbps but have different link encodings.
Ok, then for choices 6-8: 6. Have ibstat just report the rate without specifying the link encoding 7. Use umad_port:rate to encode the rate, link encoding, inter-packet delay, etc. (I'm only partially kidding here.) 8. Drop ibstat from windows. Windows users will be directed to use ibv_devinfo. Ira, what are your thoughts on this? _______________________________________________ ofw mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ofw
