On Mon, 13 Sep 2004, Alex Williamson wrote: > > Gettimeofday() = 1095104931.812600000 > CLOCK_REALTIME= 1095104931.812639404 resolution= 3712.000240992 > CLOCK_MONOTONIC= 369.103451704 resolution= 3712.000240992 > CLOCK_PROCESS_CPUTIME_ID= 0.000782450 resolution= 0.000000001 > CLOCK_THREAD_CPUTIME_ID= 0.000794115 resolution= 0.000000001 > That looks better but the resolution is still screwed up. The nanoseconds should be 3712 not the seconds.... The kernel clock_getres always sets the second part to zero. So does glibc when emulating CLOCK_REALTIME.... Could you figure out what is going on there? If the nsecs are 3712 or 4000 or so then all is fine. My small program does not check for errors and may be screwing up here. Adding some error reporting may help. Or could you give me access to a system with hpet timer? I could also test some other things like the accuracy of time interpolation. - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Mon Sep 13 16:36:59 2004
This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:30 EST