Quoting r. Nishanth Aravamudan <[EMAIL PROTECTED]>: > Looks like 5162/5163 is fine building wise. Here is what I got for > rdma_lat for a 32-bit server and 32-bit client: > > loading libehca local address: LID 0x0d QPN 0x140406 PSN 0x253f3e RKey > 0x2340032 VAddr 0x00000010019001 > remote address: LID 0x08 QPN 0x140406 PSN 0xa79d77 RKey 0x2340032 VAddr > 0x00000010019001 > Latency typical: 3.25746e+09 usec > Latency best : 3.19975e+09 usec > Latency worst : 4.21767e+10 usec > > and for rdma_bw: > > loading libehca local address: LID 0x0d, QPN 0x150406, PSN 0x1b3ee5 RKey > 0x23a0032 VAddr 0x000000f7fce000 > remote address: LID 0x08, QPN 0x150406, PSN 0x2fa0a9, RKey 0x23a0032 VAddr > 0x000000f7fb8000 > Bandwidth peak (#0 to #999): 4.3446e-07 MB/sec > Bandwidth average: 4.3446e-07 MB/sec > Service Demand peak (#0 to #999): 17301 cycles/KB > Service Demand Avg : 0 cycles/KB > > So it's still present... >
I have just uploaded a simple utility which I called clock_test which measures a clock once a second: this way you'll know whether mtfb is measuring time properly. Update to the latest bits and give it a try. -- MST _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
