Messages in this thread | | | Date | Thu, 23 Jun 2016 13:47:59 +0200 | From | Cyril Hrubis <> | Subject | Re: [LTP] [patch V2 00/20] timer: Refactor the timer wheel |
| |
Hi! > > While this is true, checking with reasonable error margin works just > > fine 99% of the time. You cannot really test that timer expires, without > > setting arbitrary margin. > > Err. You know that the timer expired because sigtimedwait() returns > EAGAIN. And the only thing you can reliably check for is that the timer did > not expired to early. Anything else is guesswork and voodoo programming.
There is quite a lot of things that can happen on mutitasking OS and there are even NMIs in hardware, etc. But seriously is there a reason why OS that is not under heavy load cannot expire timers with reasonable overruns? I.e. if I ask for a second of sleep and expect it to be woken up not much more than half of a second later?
If we stick only to guarantees that are defined in POSIX playing music with mplayer would not be possible since it sleeps in futex() and if it wakes too late it will fail to fill buffers. In practice this worked fine for me for years.
-- Cyril Hrubis chrubis@suse.cz
| |