Home
last modified time | relevance | path

Searched refs:runqueue (Results 1 – 13 of 13) sorted by relevance

/linux/Documentation/scheduler/ !
H A Dsched-domains.rst36 rebalancing event for the current runqueue has arrived. The actual load
40 The latter function takes two arguments: the runqueue of current CPU and whether
49 If it succeeds, it looks for the busiest runqueue of all the CPUs' runqueues in
50 that group. If it manages to find such a runqueue, it locks both our initial
51 CPU's runqueue and the newly found busiest one and starts moving tasks from it
52 to our runqueue. The exact number of tasks amounts to an imbalance previously
H A Dsched-arch.rst10 By default, the switch_to arch function is called with the runqueue
12 take the runqueue lock. This is usually due to a wake up operation in
15 To request the scheduler call switch_to with the runqueue unlocked,
H A Dschedutil.rst37 time an entity spends on the runqueue. When there is only a single task these
104 A further runqueue wide sum (of runnable tasks) is maintained of:
115 the runqueue keeps an max aggregate of these clamps for all running tasks.
127 The basis is the CPU runqueue's 'running' metric, which per the above it is
H A Dsched-design-CFS.rst67 runqueue. The total amount of work done by the system is tracked using
71 The total number of running tasks in the runqueue is accounted through the
73 runqueue.
119 SMP load-balancing has been reworked/sanitized: the runqueue-walking
H A Dsched-deadline.rst183 In addition, if the task wakes up on a different runqueue, then
184 the task's utilization must be removed from the previous runqueue's active
185 utilization and must be added to the new runqueue's active utilization.
186 In order to avoid races between a task waking up on a runqueue while the
188 flag is used to indicate that a task is not on a runqueue but is active
193 its utilization is removed from the runqueue's active utilization.
196 its utilization is added to the active utilization of the runqueue where
199 For each runqueue, the algorithm GRUB keeps track of two different bandwidths:
205 runqueue, including the tasks in Inactive state.
222 - Uinact is the (per runqueue) inactiv
[all...]
H A Dsched-stats.rst25 release). Some counters make more sense to be per-runqueue; other to be
197 2) time spent waiting on a runqueue (in nanoseconds)
H A Dsched-util-clamp.rst133 which have implications on the utilization value at CPU runqueue (rq for short)
/linux/drivers/gpu/drm/exynos/ !
H A Dexynos_drm_g2d.c144 * If set, suspends the runqueue worker after the currently
254 /* runqueue*/
256 struct list_head runqueue; member
815 if (list_empty(&g2d->runqueue)) in g2d_get_runqueue_node()
818 runqueue_node = list_first_entry(&g2d->runqueue, in g2d_get_runqueue_node()
843 * g2d_remove_runqueue_nodes - remove items from the list of runqueue nodes
847 * Has to be called under runqueue lock.
853 if (list_empty(&g2d->runqueue)) in g2d_remove_runqueue_nodes()
856 list_for_each_entry_safe(node, n, &g2d->runqueue, list) { in g2d_remove_runqueue_nodes()
873 * to poke the runqueue worke in g2d_runqueue_worker()
[all...]
/linux/tools/perf/Documentation/ !
H A Dperf-sched.txt227 by a task waiting on a runqueue but not getting the chance to run there
228 and is migrated to a different runqueue where it is finally run. This
/linux/Documentation/virt/kvm/ !
H A Dhalt-polling.rst18 interval or some other task on the runqueue is runnable the scheduler is
/linux/Documentation/admin-guide/hw-vuln/ !
H A Dcore-scheduling.rst116 have tasks on its on runqueue to run, however it will still have to run idle.
/linux/Documentation/admin-guide/cgroup-v1/ !
H A Dcpusets.rst552 And if a CPU run out of tasks in its runqueue, the CPU try to pull
/linux/Documentation/RCU/Design/Requirements/ !
H A DRequirements.rst2114 scheduler's runqueue or priority-inheritance spinlocks across an