Chris Friesen wrote:
George Anzinger wrote:
Bhavesh P. Davda wrote:
setitimer for 20ms was firing at 21ms
If we do NOT account for this PIT issue, the result is a time drift
that is outside of what ntp can handle...
Still, it is non-intuitive that a multi-GHz machine can't wake you up
more accurately than 1ms.
What about telling it to wake up a jiffy earlier, then checking whether
the scheduling lag was enough to cause it to have waited the full
specified time. If not, put it to sleep for another jiffy.
The user is, of course, free to do what ever they would like. For a more
complete solution you might be interested in HRT (High Res Timers). See my
signature below.
--
George Anzinger [email protected]
High-res-timers: http://sourceforge.net/projects/high-res-timers/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
