Linus Torvalds wrote:
If you calculate the expected timeout from the time-of-day in the caller,your drift not only goes away, but you'll actually be able to handle things like "oops, the machine is under load so I missed an event".
Does mainline have a high precision monotonic wallclock that is not affected by time-of-day changes? Something like "nano/mico seconds since boot"?
Chris - 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/
- Follow-Ups:
- References:
- Odd Timer behavior in 2.6 vs 2.4 (1 extra tick)
- From: [email protected]
- [PATCH] Bad rounding in timeval_to_jiffies [was: Re: Odd Timer behavior in 2.6 vs 2.4 (1 extra tick)]
- From: Steven Rostedt <[email protected]>
- Re: [PATCH] Bad rounding in timeval_to_jiffies [was: Re: Odd Timer behavior in 2.6 vs 2.4 (1 extra tick)]
- From: Steven Rostedt <[email protected]>
- Re: [PATCH] Bad rounding in timeval_to_jiffies [was: Re: Odd Timer behavior in 2.6 vs 2.4 (1 extra tick)]
- From: Russell King <[email protected]>
- Re: [PATCH] Bad rounding in timeval_to_jiffies [was: Re: Odd Timer behavior in 2.6 vs 2.4 (1 extra tick)]
- From: Steven Rostedt <[email protected]>
- Re: [PATCH] Bad rounding in timeval_to_jiffies [was: Re: Odd Timer behavior in 2.6 vs 2.4 (1 extra tick)]
- From: Linus Torvalds <[email protected]>
- Odd Timer behavior in 2.6 vs 2.4 (1 extra tick)
- Prev by Date: Re: Linux 2.6.12-rc3
- Next by Date: Re: Need AES benchmark on Intel 64 bit
- Previous by thread: Re: [PATCH] Bad rounding in timeval_to_jiffies [was: Re: Odd Timer behavior in 2.6 vs 2.4 (1 extra tick)]
- Next by thread: Re: [PATCH] Bad rounding in timeval_to_jiffies [was: Re: Odd Timer behavior in 2.6 vs 2.4 (1 extra tick)]
- Index(es):
 |