Lines Matching refs:tick
35 "tick" is the internal count in which the kernel does all its internal
37 delivered on tick boundaries to the extent practical, and no
38 fractional ticks are tracked. The choice of tick rate is configurable
50 "us" (microseconds), "tick", or "cyc" can be converted to any other.
127 being 32 bits. Large uptime counts in non-tick units will experience
156 guaranteed at the tick level no matter how many events exist or how
168 Kernel timing at the tick level is driven by a timer driver with a
176 interrupt latency interactions) that they occur near tick boundaries
177 (i.e. not "halfway through" a tick), and most importantly that they
190 fractional tick gets "reset" incorrectly and causes clock skew.
205 the OS tick rate, calling :c:func:`sys_clock_announce` with an argument of one
209 tick will be announced regardless of timeout status.
212 as no more than one tick can be detected as having elapsed (because
232 simultaneously, that only one will provide the current tick count to
233 the timing subsystem. The other may legally provide a tick count of
256 An auxiliary job of the timing subsystem is to provide tick counters
330 an uptime tick at which it will expire. So such a loop might look like: