Home
last modified time | relevance | path

Searched refs:slice (Results 1 – 8 of 8) sorted by relevance

/Zephyr-Core-2.7.6/doc/reference/kernel/scheduling/
Dindex.rst173 are measured in system clock ticks. The time slice size is configurable,
176 At the end of every time slice, the scheduler checks to see if the current
193 for longer than a single time slice without being required to yield.
/Zephyr-Core-2.7.6/kernel/
Dsched.c380 void k_sched_time_slice_set(int32_t slice, int prio) in k_sched_time_slice_set() argument
384 slice_time = k_ms_to_ticks_ceil32(slice); in k_sched_time_slice_set()
385 if (IS_ENABLED(CONFIG_TICKLESS_KERNEL) && slice > 0) { in k_sched_time_slice_set()
DKconfig451 int "Time slice size (in ms)"
458 A time slice size of zero means "no limit" (i.e. an infinitely large
459 time slice).
/Zephyr-Core-2.7.6/scripts/ci/
Dpylintrc139 invalid-slice-index,
/Zephyr-Core-2.7.6/include/
Dkernel.h886 extern void k_sched_time_slice_set(int32_t slice, int prio);
/Zephyr-Core-2.7.6/doc/reference/kernel/timing/
Dclocks.rst244 A thread time-slice cannot be a timeout value, as it does not reflect
/Zephyr-Core-2.7.6/doc/releases/
Drelease-notes-2.3.rst1223 * :github:`22745` - schedule_api fails with slice testing on frdmkw41z board on v2.2.0_rc1
Drelease-notes-2.5.rst1028 …les/scheduler/metairq_dispatch: Regression after 30916 (sched: timeout: Do not miss slice timeouts)