Lines Matching refs:code

12 conclusion that the timer wheel code is fundamentally not suitable for
20   mess. The timers.c code is very "tightly coded" around jiffies and
25   code is very good and tight code, there's zero problems with it in its
34   degrading other portions of the timers.c code in an unacceptable way.
43 - the timer wheel code is most optimal for use cases which can be
88 - simplification of existing, timing related kernel code
96 a separate list is used to give the expiry code fast access to the
109 time-changing code had to fix them up one by one, and all of them had to
112 scaling code from the posix-timer implementation - the clock can simply
117 existing timer wheel code, as it is mature and well suited. Sharing code
123 potential for code sharing either.
141 the hrtimer code will round timer events to lower-resolution clocks
166 The code was successfully compiled for the following platforms:
170 The code was run-tested on the following platforms:
176 code got a healthy amount of testing and use in practice.