| /Linux-v5.4/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 | hugetlb.rst | 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.
24 # echo $$ > g1/tasks
|
| D | memcg_test.rst | 197 /bin/echo $pid >$2/tasks 2>/dev/null
204 G1_TASK=`cat ${G1}/tasks`
205 G2_TASK=`cat ${G2}/tasks`
270 # echo 0 > /cgroup/test/tasks
276 # move all tasks in /cgroup/test to /cgroup
286 Out-of-memory caused by memcg's limit will kill tasks under
290 In this case, panic_on_oom shouldn't be invoked and tasks
317 #echo $$ >/cgroup/A/tasks
325 #echo "pid of the program running in group A" >/cgroup/B/tasks
346 # echo $$ >/cgroup/A/tasks
|
| D | cpusets.rst | 42 Nodes to a set of tasks. In this document "Memory Node" refers to
45 Cpusets constrain the CPU and Memory placement of tasks to only
80 the available CPU and Memory resources amongst the requesting tasks.
137 - You can list all the tasks (by pid) attached to any cpuset.
146 - in sched.c migrate_live_tasks(), to keep migrating tasks within
182 - cpuset.sched_relax_domain_level: the searching range when migrating tasks
190 CPUs and Memory Nodes, and attached tasks, are modified by writing
198 on a system into related sets of tasks such that each set is constrained
204 the detailed placement done on individual tasks and memory regions
251 of the rate that the tasks in a cpuset are attempting to free up in
[all …]
|
| /Linux-v5.4/samples/bpf/ |
| D | tracex2_user.c | 84 static struct task tasks[1024]; in print_hist() local
92 if (memcmp(&tasks[i], &next_key, SIZE) == 0) in print_hist()
95 memcpy(&tasks[task_cnt++], &next_key, SIZE); in print_hist()
101 (__u32) tasks[i].pid_tgid, in print_hist()
102 tasks[i].comm, in print_hist()
103 (__u32) tasks[i].uid_gid); in print_hist()
104 print_hist_for_pid(fd, &tasks[i]); in print_hist()
|
| D | map_perf_test_user.c | 90 static int pre_test_lru_hash_lookup(int tasks) in pre_test_lru_hash_lookup() argument
288 typedef int (*pre_test_func)(int tasks);
308 static int pre_test(int tasks) in pre_test() argument
314 int ret = pre_test_funcs[i](tasks); in pre_test()
339 static void run_perf_test(int tasks) in run_perf_test() argument
341 pid_t pid[tasks]; in run_perf_test()
344 assert(!pre_test(tasks)); in run_perf_test()
346 for (i = 0; i < tasks; i++) { in run_perf_test()
356 for (i = 0; i < tasks; i++) { in run_perf_test()
|
| D | test_overhead_user.c | 95 static void run_perf_test(int tasks, int flags) in run_perf_test() argument
97 pid_t pid[tasks]; in run_perf_test()
100 for (i = 0; i < tasks; i++) { in run_perf_test()
110 for (i = 0; i < tasks; i++) { in run_perf_test()
|
| /Linux-v5.4/Documentation/scheduler/ |
| 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-deadline.rst | 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
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
132 The following diagram illustrates the state names for tasks handled by GRUB::
201 tasks in active state (i.e., ActiveContending or ActiveNonContending);
203 - Total bandwidth (this_bw): this is the sum of all tasks "belonging" to the
[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 …]
|
| /Linux-v5.4/drivers/gpu/drm/ |
| D | drm_flip_work.c | 117 struct list_head tasks; in flip_worker() local
123 INIT_LIST_HEAD(&tasks); in flip_worker()
125 list_splice_tail(&work->commited, &tasks); in flip_worker()
129 if (list_empty(&tasks)) in flip_worker()
132 list_for_each_entry_safe(task, tmp, &tasks, node) { in flip_worker()
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/Documentation/admin-guide/kdump/ |
| D | gdbmacros.txt | 17 set $tasks_off=((size_t)&((struct task_struct *)0)->tasks)
20 set $next_t=(((char *)($init_t->tasks).next) - $tasks_off)
51 set $next_t=(char *)($next_t->tasks.next) - $tasks_off
83 set $tasks_off=((size_t)&((struct task_struct *)0)->tasks)
86 set $next_t=(((char *)($init_t->tasks).next) - $tasks_off)
97 set $next_t=(char *)($next_t->tasks.next) - $tasks_off
106 set $tasks_off=((size_t)&((struct task_struct *)0)->tasks)
109 set $next_t=(((char *)($init_t->tasks).next) - $tasks_off)
127 set $next_t=(char *)($next_t->tasks.next) - $tasks_off
139 set $tasks_off=((size_t)&((struct task_struct *)0)->tasks)
[all …]
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | perf-timechart.txt | 48 --tasks-only::
60 Print task info for at least given number of tasks.
65 Highlight tasks (using different color) that run more than given
66 duration or tasks with given name. If number is given it's interpreted
89 --tasks-only::
90 Record only tasks-related events
114 then generate timechart and highlight 'gcc' tasks:
|
| /Linux-v5.4/kernel/sched/ |
| D | psi.c | 215 static bool test_state(unsigned int *tasks, enum psi_states state) in test_state() argument
219 return tasks[NR_IOWAIT]; in test_state()
221 return tasks[NR_IOWAIT] && !tasks[NR_RUNNING]; in test_state()
223 return tasks[NR_MEMSTALL]; in test_state()
225 return tasks[NR_MEMSTALL] && !tasks[NR_RUNNING]; in test_state()
227 return tasks[NR_RUNNING] > 1; in test_state()
229 return tasks[NR_IOWAIT] || tasks[NR_MEMSTALL] || in test_state()
230 tasks[NR_RUNNING]; in test_state()
696 if (groupc->tasks[t] == 0 && !psi_bug) { in psi_group_change()
698 cpu, t, groupc->tasks[0], in psi_group_change()
[all …]
|
| /Linux-v5.4/Documentation/x86/x86_64/ |
| D | fake-numa-for-cpusets.rst | 14 assign them to cpusets and their attached tasks. This is a way of limiting the
15 amount of system memory that are available to a certain class of tasks.
56 You can now assign tasks to these cpusets to limit the memory resources
59 [root@xroads /exampleset/ddset]# echo $$ > tasks
75 This allows for coarse memory management for the tasks you assign to particular
77 interesting combinations of use-cases for various classes of tasks for your
|
| /Linux-v5.4/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 …]
|
| /Linux-v5.4/Documentation/ |
| D | futex-requeue-pi.txt | 5 Requeueing of tasks from a non-PI futex to a PI futex requires
17 pthread_cond_broadcast() must resort to waking all the tasks waiting
47 Once pthread_cond_broadcast() requeues the tasks, the cond->mutex
54 be able to requeue tasks to PI futexes. This support implies that
113 possibly wake the waiting tasks. Internally, this system call is
118 nr_wake+nr_requeue tasks to the PI futex, calling
126 requeue up to nr_wake + nr_requeue tasks. It will wake only as many
127 tasks as it can acquire the lock for, which in the majority of cases
|
| /Linux-v5.4/net/sunrpc/ |
| D | sched.c | 192 __rpc_list_enqueue_task(&queue->tasks[queue_priority], task); in __rpc_add_wait_queue_priority()
215 list_add(&task->u.tk_wait.list, &queue->tasks[0]); in __rpc_add_wait_queue()
217 list_add_tail(&task->u.tk_wait.list, &queue->tasks[0]); in __rpc_add_wait_queue()
257 for (i = 0; i < ARRAY_SIZE(queue->tasks); i++) in __rpc_init_priority_wait_queue()
258 INIT_LIST_HEAD(&queue->tasks[i]); in __rpc_init_priority_wait_queue()
612 q = &queue->tasks[queue->priority]; in __rpc_find_next_queued_priority()
622 if (q == &queue->tasks[0]) in __rpc_find_next_queued_priority()
623 q = &queue->tasks[queue->maxpriority]; in __rpc_find_next_queued_priority()
630 } while (q != &queue->tasks[queue->priority]); in __rpc_find_next_queued_priority()
636 rpc_set_waitqueue_priority(queue, (unsigned int)(q - &queue->tasks[0])); in __rpc_find_next_queued_priority()
[all …]
|
| /Linux-v5.4/Documentation/RCU/ |
| D | stallwarn.txt | 93 The RCU, RCU-sched, and RCU-tasks implementations have CPU stall warning.
159 This boot/sysfs parameter controls the RCU-tasks stall warning
160 interval. A value of zero or less suppresses RCU-tasks stall
162 in seconds. An RCU-tasks stall warning starts with the line:
164 INFO: rcu_tasks detected stalls on tasks:
167 task stalling the current RCU-tasks grace period.
172 For non-RCU-tasks flavors of RCU, when a CPU detects that it is stalling,
175 INFO: rcu_sched detected stalls on CPUs/tasks:
183 PREEMPT_RCU builds can be stalled by tasks as well as by CPUs, and that
184 the tasks will be indicated by PID, for example, "P3421". It is even
[all …]
|
| /Linux-v5.4/Documentation/admin-guide/namespaces/ |
| D | compatibility-list.rst | 6 may have when creating tasks living in different namespaces.
9 occur when tasks share some namespace (the columns) while living
27 In both cases, tasks shouldn't try exposing this ID to some
|
| /Linux-v5.4/scripts/gdb/linux/ |
| D | cpus.py | 16 from linux import tasks, utils
30 return tasks.get_thread_info(tasks.get_task_by_pid(tid))['cpu']
|
