This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: clock_getres(CLOCK_REALTIME, .) may return an outdated and too high resolution

On Mar 26 19:00, Christian Franke wrote:
> Corinna Vinschen wrote:
> >I see your point, but what bugs me a bit is the fact that
> >clock_getres(CLOCK_REALTIME) and clock_setres(CLOCK_REALTIME) will
> >always return the same value coarsest, regardless what value has been set.
> If clock_setres was called and succeeded, then clock_getres(.)
> should return the value set before.
> If clock_setres was not called, the coarsest value is IMO the only
> value that can be guaranteed.
> The actual value returned by NtQueryTimerResolution is simply
> useless in this context: It is the minimum of all resolutions
> currently set by all running processes. It may change at any time.
> There is apparently no way the query the current setting of the
> current process.

Uh, right, I misunderstood.  I reverted the change to clock_setres.

> clock_gettime is part of the POSIX realtime extensions. On Linux it
> requires -lrt which implies -lpthreads. So if clock_gettime is used
> we can probably assume that the program wants a finer resolution.

Not really.  The usage of clock_gettime only implies that somebody wants
to measure time in a certain way depending on the used clock.  It does
not imply any resolution requirements.  And POSIX does not require any
specific resolutions, rather they are "implementation-defined".

> This leads to a possible alternative if clock_setres is not used: On
> first call of clock_gettime/getres set a finer (the finest?)
> resolution and return this with clock_getres.
> Drawback: The finer resolution will persist until this process and
> all childs terminate. This may have unknown impact on performance,
> power management or whatever.
> This could be fixed by resetting the resolution to default if
> clock_gettime is no longer used for some time (e.g. >= 10min).
> Drawback: Even more complexity :-)

Nah, let's not go that route.  If you want a finer resolution by
default, I think there might be some other solution...

> >>- Unlike on e.g. Linux, CLOCK_REALTIME does not provide a better
> >>resolution than gettimeofday().
> >We can only use what the OS provides.  Starting with Windows 8 there
> >will be a new function call GetSystemTimePreciseAsFileTime:
> >
> This would provide an easy solution for >= Win8: clock_gettime
> returns GetSystemTimePreciseAsFileTime, clock_getres returns
> constant 1us.

As far as I can tell from a quick debug session, the implementation
of the underlying RtlGetSystemTimePrecise function is based on a spiffy
combination of the standard clock tick with the performance counter.
I'm not very good at assembler debugging, but the essence is access
to some known and some unknown time values from SharedUserData, a
call to RtlQueryPerformanceCounter, and a bit of arithmetic.

Maybe we can implement something similar without waiting for W8?  Does
anybody have code to combine a not so precise clock with a more precise
counter to create a more precise clock?


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]