Lines Matching +full:operations +full:- +full:per +full:- +full:run

46 ----------
66 word, these conversions expand to a 2-4 operation sequence, requiring
91 * Kernel blocking operations like :c:func:`k_sem_take` or
127 being 32 bits.  Large uptime counts in non-tick units will experience
129 timing-sensitive applications with long uptimes will be configured to
142 -------------
146 a double-linked list, with an attendant delta count in ticks from the
150 expected to be embedded within subsystem-defined data structures (for
155 multiple-conversion steps internal to the kernel, so precision is
166 -------------
217 -----------
219 In general, the timer API described above does not change when run in
231   per-CPU tracking, and expects that if two timer interrupts fire near
238   per-CPU counter.  The complexity here (for example: ensuring counter
246   non-zero ticks argument to :c:func:`sys_clock_announce`.  This is probably
254 ------------
258 A thread time-slice cannot be a timeout value, as it does not reflect
259 a global expiration but instead a per-CPU value that needs to be
269 -------------------------------------
285 will need to use a different, integer-valued token to represent
291 --------------------------------
304 that may require multiple blocking operations on underlying kernel
307 .. code-block:: c
319             k_sem_take(obj->sem, timeout_in_ms);
322             timeout_in_ms -= (k_uptime_get_32() - start);
333 .. code-block:: c
349             k_sem_take(obj->sem, timeout);