| /linux-6.1.9/kernel/sched/ |
| D | pelt.c | 103 unsigned long load, unsigned long runnable, int running) in accumulate_sum() argument
143 if (runnable) in accumulate_sum()
144 sa->runnable_sum += runnable * contrib << SCHED_CAPACITY_SHIFT; in accumulate_sum()
181 unsigned long load, unsigned long runnable, int running) in ___update_load_sum() argument
217 runnable = running = 0; in ___update_load_sum()
226 if (!accumulate_sum(delta, sa, load, runnable, running)) in ___update_load_sum()
|
| D | fair.c | 1681 unsigned long runnable; member
1734 ((ns->compute_capacity * imbalance_pct) < (ns->runnable * 100)))) in numa_classify()
1739 ((ns->compute_capacity * imbalance_pct) > (ns->runnable * 100)))) in numa_classify()
1790 ns->runnable += cpu_runnable(rq); in update_numa_stats()
6266 unsigned int runnable; in cpu_runnable_without() local
6273 runnable = READ_ONCE(cfs_rq->avg.runnable_avg); in cpu_runnable_without()
6276 lsub_positive(&runnable, p->se.avg.runnable_avg); in cpu_runnable_without()
6278 return runnable; in cpu_runnable_without()
|
| /linux-6.1.9/Documentation/scheduler/ |
| D | schedutil.rst | 35 Using this we track 2 key metrics: 'running' and 'runnable'. 'Running'
36 reflects the time an entity spends on the CPU, while 'runnable' reflects the
40 while 'runnable' will increase to reflect the amount of contention.
83 The result is that the above 'running' and 'runnable' metrics become invariant
105 A further runqueue wide sum (of runnable tasks) is maintained of:
|
| D | sched-design-CFS.rst | 44 up CPU time between runnable tasks as close to "ideal multitasking hardware" as
71 CFS maintains a time-ordered rbtree, where all runnable tasks are sorted by the
167 Called when a task enters a runnable state.
173 When a task is no longer runnable, this function is called to keep the
185 This function checks if a task that entered the runnable state should
|
| D | sched-bwc.rst | 15 slices as threads in the cgroup become runnable. Once all quota has been
202 decide which application is chosen to run, as they will both be runnable and
|
| D | sched-capacity.rst | 242 accurately be predicted the moment a task first becomes runnable. The CFS class
|
| /linux-6.1.9/Documentation/timers/ |
| D | no_hz.rst | 24 have only one runnable task (CONFIG_NO_HZ_FULL=y). Unless you
44 will frequently be multiple runnable tasks per CPU. In these cases,
107 If a CPU has only one runnable task, there is little point in sending it
109 Note that omitting scheduling-clock ticks for CPUs with only one runnable
113 sending scheduling-clock interrupts to CPUs with a single runnable task,
260 runnable task for a given CPU, even though there are a number
263 runnable high-priority SCHED_FIFO task and an arbitrary number
270 single runnable SCHED_FIFO task and multiple runnable SCHED_OTHER
273 And even when there are multiple runnable tasks on a given CPU,
|
| /linux-6.1.9/Documentation/accounting/ |
| D | delay-accounting.rst | 7 runnable task may wait for a free CPU to run on.
12 a) waiting for a CPU (while being runnable)
|
| D | taskstats-struct.rst | 112 /* Delay waiting for cpu, while runnable
|
| /linux-6.1.9/Documentation/virt/ |
| D | guest-halt-polling.rst | 18 even with other runnable tasks in the host.
|
| /linux-6.1.9/Documentation/virt/kvm/ |
| D | halt-polling.rst | 18 interval or some other task on the runqueue is runnable the scheduler is
150 - Halt polling will only be conducted by the host when no other tasks are runnable on
|
| D | api.rst | 5454 KVM automatically accounts running and runnable time but blocked
6285 marking the exiting vCPU as runnable, or deny it and call KVM_RUN again.
|
| /linux-6.1.9/Documentation/core-api/ |
| D | workqueue.rst | 118 number of the currently runnable workers. Generally, work items are
121 stalling should be optimal. As long as there are one or more runnable
205 concurrency level. In other words, runnable CPU intensive
213 regulated by the concurrency management and runnable
|
| /linux-6.1.9/Documentation/admin-guide/pm/ |
| D | cpuidle.rst | 90 Tasks can be in various states. In particular, they are *runnable* if there are
93 events to occur or similar). When a task becomes runnable, the CPU scheduler
94 assigns it to one of the available CPUs to run and if there are no more runnable
97 another CPU). [If there are multiple runnable tasks assigned to one CPU
101 The special "idle" task becomes runnable if there are no other runnable tasks
193 multiple runnable tasks assigned to one CPU at the same time, the only way to
216 not be shared between multiple runnable tasks, the primary reason for using the
|
| /linux-6.1.9/Documentation/arm64/ |
| D | asymmetric-32bit.rst | 154 ``KVM_EXIT_FAIL_ENTRY`` and will remain non-runnable until successfully
|
| /linux-6.1.9/Documentation/s390/ |
| D | vfio-ccw.rst | 331 space, and assemble a runnable kernel channel program by updating the
382 channel program, which becomes runnable for a real device.
|
| /linux-6.1.9/Documentation/admin-guide/hw-vuln/ |
| D | core-scheduling.rst | 108 highest priority task with the same cookie is selected if there is one runnable
|
| /linux-6.1.9/Documentation/admin-guide/ |
| D | kernel-per-CPU-kthreads.rst | 159 for example, ensure that at most one runnable kthread is present
|
| /linux-6.1.9/Documentation/process/ |
| D | license-rules.rst | 356 with this exception. This is required for creating runnable executables
|
| /linux-6.1.9/Documentation/filesystems/ |
| D | proc.rst | 702 number of processes currently runnable (running or on ready queue);
706 processes currently runnable" and "total number of processes
1501 running or ready to run (i.e., the total number of runnable threads).
2135 out. With CPU isolation and a single runnable task this can take
|
| /linux-6.1.9/Documentation/locking/ |
| D | rt-mutex-design.rst | 69 of A. So now if B becomes runnable, it would not preempt C, since C now has
|