Lines Matching full:timers

2 hrtimers - subsystem for high-resolution kernel timers
5 This patch introduces a new subsystem for high-resolution kernel timers.
8 (kernel/timers.c), why do we need two timer subsystems? After a lot of
18 - the forced handling of low-resolution and high-resolution timers in
20   mess. The timers.c code is very "tightly coded" around jiffies and
27   high-res timers.
30   necessitate a more complex handling of high resolution timers, which
34   degrading other portions of the timers.c code in an unacceptable way.
38   the required readjusting of absolute CLOCK_REALTIME timers at
41   timers.
46   I/O. The vast majority of those timers never expire and are rarely
58 The primary users of precision timers are user-space applications that
59 utilize nanosleep, posix-timers and itimer interfaces. Also, in-kernel
68 with other potential users for precise timers gives another reason to
91 timers at activation time. After looking at several possible solutions
97 queued timers, without having to walk the rbtree.
105 absolute timers based on a low-resolution CLOCK_REALTIME. The existing
107 CLOCK_REALTIME timers along with complex locking. In case of
108 settimeofday and NTP, all the timers (!) had to be dequeued, the
114 of posix-timers simpler in general.
156  - posix-timers
158 The conversion of nanosleep and posix-timers enabled the unification of