<br><font size=2><tt>> in case someone's firmware is less accurate than
HP's.</tt></font>
<br><font size=2><tt>> Shirley, did the patch to get_clock.c fix the
problem?</tt></font>
<br>
<br><font size=2 face="sans-serif">Cycles is not equal to the clock rate.
If you have a processor with internal doubling or pipelining or whatever,
the clock rate isn't the same.</font>
<br>
<br><font size=2><tt>> Maybe there shall be a separate utility to compare<br>
> get_cycles and gettimeofday results, may be useful for debug.<br>
> <br>
> Anyway, if get_cpu_mhz isnt reliable people can just dump raw<br>
> cycles data and do the math outside the tool.</tt></font>
<br>
<br><font size=2 face="sans-serif">Agree if the rdma_lat, and rdma_bw are
only used for debugging/regression testing not for performance measurement.</font>
<br><font size=2 face="sans-serif"><br>
Thanks<br>
Shirley Ma<br>
IBM Linux Technology Center<br>
15300 SW Koll Parkway<br>
Beaverton, OR 97006-6063<br>
Phone(Fax): (503) 578-7638<br>
<br>
</font>