| /kernel/linux/linux-5.10/Documentation/admin-guide/cgroup-v1/ |
| D | freezer-subsystem.rst | 6 and stop sets of tasks in order to schedule the resources of a machine
9 whole. The cgroup freezer uses cgroups to describe the set of tasks to
11 a means to start and stop the tasks composing the job.
14 of tasks. The freezer allows the checkpoint code to obtain a consistent
15 image of the tasks by attempting to force the tasks in a cgroup into a
16 quiescent state. Once the tasks are quiescent another task can
18 quiesced tasks. Checkpointed tasks can be restarted later should a
19 recoverable error occur. This also allows the checkpointed tasks to be
21 to another node and restarting the tasks there.
24 and resuming tasks in userspace. Both of these signals are observable
[all …]
|
| D | cpuacct.rst | 5 The CPU accounting controller is used to group tasks using cgroups and
6 account the CPU usage of these groups of tasks.
9 group accumulates the CPU usage of all of its child groups and the tasks
17 visible at /sys/fs/cgroup. At bootup, this group includes all the tasks in
18 the system. /sys/fs/cgroup/tasks lists the tasks in this cgroup.
20 by this group which is essentially the CPU time obtained by all the tasks
27 # echo $$ > g1/tasks
38 user: Time spent by tasks of the cgroup in user mode.
39 system: Time spent by tasks of the cgroup in kernel mode.
|
| D | cgroups.rst | 45 tasks, and all their future children, into hierarchical groups with
50 A *cgroup* associates a set of tasks with a set of parameters for one
54 facilities provided by cgroups to treat groups of tasks in
67 cgroups. Each hierarchy is a partition of all tasks in the system.
81 tasks in each cgroup.
100 the division of tasks into cgroups is distinctly different for
102 hierarchy to be a natural division of tasks, without having to handle
103 complex combinations of tasks that would be present if several
114 tasks etc. The resource planning for this server could be along the
123 In addition (system tasks) are attached to topcpuset (so
[all …]
|
| D | cpusets.rst | 44 Nodes to a set of tasks. In this document "Memory Node" refers to
47 Cpusets constrain the CPU and Memory placement of tasks to only
82 the available CPU and Memory resources amongst the requesting tasks.
139 - You can list all the tasks (by pid) attached to any cpuset.
148 - in sched.c migrate_live_tasks(), to keep migrating tasks within
184 - cpuset.sched_relax_domain_level: the searching range when migrating tasks
192 CPUs and Memory Nodes, and attached tasks, are modified by writing
200 on a system into related sets of tasks such that each set is constrained
206 the detailed placement done on individual tasks and memory regions
264 of the rate that the tasks in a cpuset are attempting to free up in
[all …]
|
| /kernel/linux/linux-4.19/Documentation/cgroup-v1/ |
| D | freezer-subsystem.txt | 2 and stop sets of tasks in order to schedule the resources of a machine
5 whole. The cgroup freezer uses cgroups to describe the set of tasks to
7 a means to start and stop the tasks composing the job.
10 of tasks. The freezer allows the checkpoint code to obtain a consistent
11 image of the tasks by attempting to force the tasks in a cgroup into a
12 quiescent state. Once the tasks are quiescent another task can
14 quiesced tasks. Checkpointed tasks can be restarted later should a
15 recoverable error occur. This also allows the checkpointed tasks to be
17 to another node and restarting the tasks there.
20 and resuming tasks in userspace. Both of these signals are observable
[all …]
|
| D | cpuacct.txt | 4 The CPU accounting controller is used to group tasks using cgroups and
5 account the CPU usage of these groups of tasks.
8 group accumulates the CPU usage of all of its child groups and the tasks
16 visible at /sys/fs/cgroup. At bootup, this group includes all the tasks in
17 the system. /sys/fs/cgroup/tasks lists the tasks in this cgroup.
19 by this group which is essentially the CPU time obtained by all the tasks
26 # echo $$ > g1/tasks
37 user: Time spent by tasks of the cgroup in user mode.
38 system: Time spent by tasks of the cgroup in kernel mode.
|
| D | cgroups.txt | 41 tasks, and all their future children, into hierarchical groups with
46 A *cgroup* associates a set of tasks with a set of parameters for one
50 facilities provided by cgroups to treat groups of tasks in
63 cgroups. Each hierarchy is a partition of all tasks in the system.
77 tasks in each cgroup.
96 the division of tasks into cgroups is distinctly different for
98 hierarchy to be a natural division of tasks, without having to handle
99 complex combinations of tasks that would be present if several
110 tasks etc. The resource planning for this server could be along the
119 In addition (system tasks) are attached to topcpuset (so
[all …]
|
| D | cpusets.txt | 41 Nodes to a set of tasks. In this document "Memory Node" refers to
44 Cpusets constrain the CPU and Memory placement of tasks to only
79 the available CPU and Memory resources amongst the requesting tasks.
136 - You can list all the tasks (by pid) attached to any cpuset.
145 - in sched.c migrate_live_tasks(), to keep migrating tasks within
181 - cpuset.sched_relax_domain_level: the searching range when migrating tasks
188 CPUs and Memory Nodes, and attached tasks, are modified by writing
196 on a system into related sets of tasks such that each set is constrained
202 the detailed placement done on individual tasks and memory regions
249 of the rate that the tasks in a cpuset are attempting to free up in
[all …]
|
| /kernel/linux/linux-4.19/Documentation/power/ |
| D | freezing-of-tasks.txt | 1 Freezing of tasks
4 I. What is the freezing of tasks?
6 The freezing of tasks is a mechanism by which user space processes and some
13 and PF_FREEZER_SKIP (the last one is auxiliary). The tasks that have
25 All freezable tasks must react to that by calling try_to_freeze(), which
57 initiated a freezing operation, the freezing of tasks will fail and the entire
64 order to clear the PF_FROZEN flag for each frozen task. Then, the tasks that
68 Rationale behind the functions dealing with freezing and thawing of tasks:
72 - freezes only userspace tasks
75 - freezes all tasks (including kernel threads) because we can't freeze
[all …]
|
| /kernel/linux/linux-4.19/Documentation/scheduler/ |
| D | sched-design-CFS.txt | 18 1/nr_running speed. For example: if there are 2 tasks running, then it runs
25 is its actual runtime normalized to the total number of running tasks.
35 [ small detail: on "ideal" hardware, at any time all tasks would have the same
36 p->se.vruntime value --- i.e., tasks would execute simultaneously and no task
42 up CPU time between runnable tasks as close to "ideal multitasking hardware" as
59 increasing value tracking the smallest vruntime among all tasks in the
64 The total number of running tasks in the runqueue is accounted through the
65 rq->cfs.load value, which is the sum of the weights of the tasks queued on the
68 CFS maintains a time-ordered rbtree, where all runnable tasks are sorted by the
70 As the system progresses forwards, the executed tasks are put into the tree
[all …]
|
| D | sched-deadline.txt | 12 3. Scheduling Real-Time Tasks
22 5. Tasks CPU affinity
43 that makes it possible to isolate the behavior of tasks between each other.
53 "deadline", to schedule tasks. A SCHED_DEADLINE task should receive
58 consistent with the guarantee (using the CBS[2,3] algorithm). Tasks are then
65 Summing up, the CBS[2,3] algorithm assigns scheduling deadlines to tasks so
67 interference between different tasks (bandwidth isolation), while the EDF[1]
69 to be executed next. Thanks to this feature, tasks that do not strictly comply
74 tasks in the following way:
128 Bandwidth reclaiming for deadline tasks is based on the GRUB (Greedy
[all …]
|
| D | sched-rt-group.txt | 14 2.3 Basis for grouping tasks
44 multiple groups of realtime tasks, each group must be assigned a fixed portion
57 tasks (SCHED_OTHER). Any allocated run time not used will also be picked up by
72 The remaining CPU time will be used for user input and other tasks. Because
73 realtime tasks have explicitly allocated the CPU time they need to perform
74 their tasks, buffer underruns in the graphics or audio can be eliminated.
110 SCHED_OTHER (non-RT tasks). These defaults were chosen so that a run-away
111 realtime tasks will not lock up the machine but leave a little time to recover
120 bandwidth to the group before it will accept realtime tasks. Therefore you will
121 not be able to run realtime tasks as any user other than root until you have
[all …]
|
| /kernel/linux/linux-5.10/Documentation/scheduler/ |
| D | sched-deadline.rst | 12 3. Scheduling Real-Time Tasks
22 5. Tasks CPU affinity
43 that makes it possible to isolate the behavior of tasks between each other.
53 "deadline", to schedule tasks. A SCHED_DEADLINE task should receive
58 consistent with the guarantee (using the CBS[2,3] algorithm). Tasks are then
65 Summing up, the CBS[2,3] algorithm assigns scheduling deadlines to tasks so
67 interference between different tasks (bandwidth isolation), while the EDF[1]
69 to be executed next. Thanks to this feature, tasks that do not strictly comply
74 tasks in the following way:
128 Bandwidth reclaiming for deadline tasks is based on the GRUB (Greedy
[all …]
|
| D | sched-design-CFS.rst | 19 1/nr_running speed. For example: if there are 2 tasks running, then it runs
26 is its actual runtime normalized to the total number of running tasks.
37 [ small detail: on "ideal" hardware, at any time all tasks would have the same
38 p->se.vruntime value --- i.e., tasks would execute simultaneously and no task
44 up CPU time between runnable tasks as close to "ideal multitasking hardware" as
62 increasing value tracking the smallest vruntime among all tasks in the
67 The total number of running tasks in the runqueue is accounted through the
68 rq->cfs.load value, which is the sum of the weights of the tasks queued on the
71 CFS maintains a time-ordered rbtree, where all runnable tasks are sorted by the
73 As the system progresses forwards, the executed tasks are put into the tree
[all …]
|
| D | sched-rt-group.rst | 14 2.3 Basis for grouping tasks
44 multiple groups of realtime tasks, each group must be assigned a fixed portion
57 tasks (SCHED_OTHER). Any allocated run time not used will also be picked up by
72 The remaining CPU time will be used for user input and other tasks. Because
73 realtime tasks have explicitly allocated the CPU time they need to perform
74 their tasks, buffer underruns in the graphics or audio can be eliminated.
110 SCHED_OTHER (non-RT tasks). These defaults were chosen so that a run-away
111 realtime tasks will not lock up the machine but leave a little time to recover
120 bandwidth to the group before it will accept realtime tasks. Therefore you will
121 not be able to run realtime tasks as any user other than root until you have
[all …]
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | freezing-of-tasks.rst | 2 Freezing of tasks
7 I. What is the freezing of tasks?
10 The freezing of tasks is a mechanism by which user space processes and some
18 and PF_FREEZER_SKIP (the last one is auxiliary). The tasks that have
30 All freezable tasks must react to that by calling try_to_freeze(), which
62 initiated a freezing operation, the freezing of tasks will fail and the entire
69 order to clear the PF_FROZEN flag for each frozen task. Then, the tasks that
73 Rationale behind the functions dealing with freezing and thawing of tasks
77 - freezes only userspace tasks
80 - freezes all tasks (including kernel threads) because we can't freeze
[all …]
|
| /kernel/linux/linux-5.10/kernel/rcu/ |
| D | tasks.h | 23 * Definition for a Tasks-RCU-like mechanism.
84 /* Track exiting tasks in order to allow them to be waited for. */
97 /* RCU tasks grace-period state for debugging. */
151 // Enqueue a callback for the specified flavor of Tasks RCU.
170 // Wait for a grace period for the specified flavor of Tasks RCU.
181 /* RCU-tasks kthread that detects grace periods and invokes callbacks. */
196 * one RCU-tasks grace period and then invokes the callbacks. in rcu_tasks_kthread()
244 /* Spawn RCU-tasks grace-period kthread. */
258 * Print any non-default Tasks RCU settings.
267 pr_info("\tTrampoline variant of Tasks RCU enabled.\n"); in rcu_tasks_bootup_oddness()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/livepatch/ |
| D | livepatch.rst | 98 transition state where tasks are converging to the patched state.
100 sequence occurs when a patch is disabled, except the tasks converge from
104 interrupts. The same is true for forked tasks: the child inherits the
108 safe to patch tasks:
111 tasks. If no affected functions are on the stack of a given task,
113 the tasks on the first try. Otherwise it'll keep trying
121 a) Patching I/O-bound user tasks which are sleeping on an affected
124 b) Patching CPU-bound user tasks. If the task is highly CPU-bound
128 3. For idle "swapper" tasks, since they don't ever exit the kernel, they
135 the second approach. It's highly likely that some tasks may still be
[all …]
|
| /kernel/linux/linux-4.19/Documentation/livepatch/ |
| D | livepatch.txt | 98 transition state where tasks are converging to the patched state.
100 sequence occurs when a patch is disabled, except the tasks converge from
104 interrupts. The same is true for forked tasks: the child inherits the
108 safe to patch tasks:
111 tasks. If no affected functions are on the stack of a given task,
113 the tasks on the first try. Otherwise it'll keep trying
121 a) Patching I/O-bound user tasks which are sleeping on an affected
124 b) Patching CPU-bound user tasks. If the task is highly CPU-bound
128 3. For idle "swapper" tasks, since they don't ever exit the kernel, they
135 the second approach. It's highly likely that some tasks may still be
[all …]
|
| /kernel/linux/linux-5.10/kernel/livepatch/ |
| D | transition.c | 30 * "straggler" tasks which failed to transition in the first attempt.
46 * tasks even in userspace and idle.
87 * All tasks have transitioned to KLP_UNPATCHED so we can now in klp_complete_transition()
297 * on other methods (e.g., switching tasks at kernel exit). in klp_try_switch_task()
340 * Sends a fake signal to all non-kthread tasks with TIF_PATCH_PENDING set.
348 pr_notice("signaling remaining tasks\n"); in klp_send_signals()
369 * Send fake signal to all non-kthread tasks which are in klp_send_signals()
381 * Try to switch all remaining tasks to the target patch state by walking the
382 * stacks of sleeping tasks and looking for any to-be-patched or
386 * If any tasks are still stuck in the initial patch state, schedule a retry.
[all …]
|
| /kernel/linux/linux-4.19/kernel/livepatch/ |
| D | transition.c | 40 * "straggler" tasks which failed to transition in the first attempt.
56 * tasks even in userspace and idle.
92 * All tasks have transitioned to KLP_UNPATCHED so we can now in klp_complete_transition()
351 * Try to switch all remaining tasks to the target patch state by walking the
352 * stacks of sleeping tasks and looking for any to-be-patched or
356 * If any tasks are still stuck in the initial patch state, schedule a retry.
367 * Try to switch the tasks to the target patch state by walking their in klp_try_complete_transition()
372 * Usually this will transition most (or all) of the tasks on a system in klp_try_complete_transition()
382 * Ditto for the idle "swapper" tasks. in klp_try_complete_transition()
391 /* offline idle tasks can be switched immediately */ in klp_try_complete_transition()
[all …]
|
| /kernel/linux/linux-4.19/Documentation/RCU/ |
| D | stallwarn.txt | 90 The RCU, RCU-sched, RCU-bh, and RCU-tasks implementations have CPU stall
156 This boot/sysfs parameter controls the RCU-tasks stall warning
157 interval. A value of zero or less suppresses RCU-tasks stall
159 in jiffies. An RCU-tasks stall warning starts with the line:
161 INFO: rcu_tasks detected stalls on tasks:
164 task stalling the current RCU-tasks grace period.
169 For non-RCU-tasks flavors of RCU, when a CPU detects that it is stalling,
172 INFO: rcu_sched detected stalls on CPUs/tasks:
180 PREEMPT_RCU builds can be stalled by tasks as well as by CPUs, and that
181 the tasks will be indicated by PID, for example, "P3421". It is even
[all …]
|
| /kernel/linux/linux-4.19/tools/perf/scripts/python/ |
| D | sched-migration.py | 102 def __init__(self, tasks = [0], event = RunqueueEventUnknown()): argument
103 self.tasks = tuple(tasks)
109 if taskState(prev_state) == "R" and next in self.tasks \
110 and prev in self.tasks:
116 next_tasks = list(self.tasks[:])
117 if prev in self.tasks:
129 if old not in self.tasks:
131 next_tasks = [task for task in self.tasks if task != old]
136 if new in self.tasks:
139 next_tasks = self.tasks[:] + tuple([new])
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/scripts/python/ |
| D | sched-migration.py | 100 def __init__(self, tasks = [0], event = RunqueueEventUnknown()): argument
101 self.tasks = tuple(tasks)
107 if taskState(prev_state) == "R" and next in self.tasks \
108 and prev in self.tasks:
114 next_tasks = list(self.tasks[:])
115 if prev in self.tasks:
127 if old not in self.tasks:
129 next_tasks = [task for task in self.tasks if task != old]
134 if new in self.tasks:
137 next_tasks = self.tasks[:] + tuple([new])
[all …]
|
| /kernel/linux/linux-4.19/tools/testing/selftests/futex/include/ |
| D | futextest.h | 88 * futex_wake() - wake one or more tasks blocked on uaddr
89 * @nr_wake: wake up to this many tasks
110 * futex_wake_bitset() - wake one or more tasks blocked on uaddr with bitset
153 * @nr_wake: wake up to this many tasks
154 * @nr_requeue: requeue up to this many tasks
168 * futex_cmp_requeue() - requeue tasks from uaddr to uaddr2
169 * @nr_wake: wake up to this many tasks
170 * @nr_requeue: requeue up to this many tasks
197 * futex_cmp_requeue_pi() - requeue tasks from uaddr to uaddr2 (PI aware)
200 * @nr_wake: wake up to this many tasks
[all …]
|