> > Inter-CPU monotonicity can not, however, be guaranteed in a vsyscall, so> vsyscall is not used by default.

Only for unsynchronized machines I hope

> Still, the syscall version of gettimeofday is > a lot faster using the TSC approximation instead of other hardware timers.

Yes that makes sense.

The big strategic problem is how to marry your patchkit to John Stultz'sclocksources work which is also competing for merge. Any thoughts on that?

>When strict inter-CPU monotonicity is not needed, the vsyscall version of>gettimeofday may be forced using the "nomonotonic" command line parameter.>gettimeofday()'s monotonicity is guaranteed on a single CPU even with the very>fast vsyscall version. Across CPUs, the vsyscall version of gettimeofday is>not guaranteed to be monotonic, but it should be pretty close. Currently, we>get errors of tens/hundreds of microseconds.

I think a better way to do this would be to define a new CLOCK_THREAD_MONOTONOUS(or better name) timer for clock_gettime().