Searched refs:runqueue (Results 1 – 8 of 8) sorted by relevance
| /linux/Documentation/scheduler/ |
| H A D | sched-arch.rst | 10 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 D | schedutil.rst | 37 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 D | sched-util-clamp.rst | 133 which have implications on the utilization value at CPU runqueue (rq for short)
|
| /linux/drivers/gpu/drm/exynos/ |
| H A D | exynos_drm_g2d.c | 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()
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()
1332 list_add_tail(&runqueue_node->list, &g2d->runqueue); in exynos_g2d_exec_ioctl()
1475 INIT_LIST_HEAD(&g2d->runqueue); in g2d_probe()
|
| /linux/Documentation/virt/kvm/ |
| H A D | halt-polling.rst | 18 interval or some other task on the runqueue is runnable the scheduler is
|
| /linux/Documentation/admin-guide/hw-vuln/ |
| H A D | core-scheduling.rst | 116 have tasks on its on runqueue to run, however it will still have to run idle.
|
| /linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | cpusets.rst | 552 And if a CPU run out of tasks in its runqueue, the CPU try to pull
|
| /linux/Documentation/RCU/Design/Requirements/ |
| H A D | Requirements.rst | 2114 scheduler's runqueue or priority-inheritance spinlocks across an
|