Searched full:tasks (Results 1 – 25 of 228) sorted by relevance
12345678910
| /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.
102 the division of tasks into cgroups is distinctly different for
104 hierarchy to be a natural division of tasks, without having to handle
105 complex combinations of tasks that would be present if several
116 tasks etc. The resource planning for this server could be along the
125 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 …]
|
| D | hugetlb.rst | 10 visible at /sys/fs/cgroup. At bootup, this group includes all the tasks in
11 the system. /sys/fs/cgroup/tasks lists the tasks in this cgroup.
17 # echo $$ > g1/tasks
109 the HugeTLB usage of all the tasks in the system and make sure there is enough
110 pages to satisfy all requests. Avoiding tasks getting SIGBUS on overcommited
|
| D | memcg_test.rst | 188 /bin/echo $pid >$2/tasks 2>/dev/null
195 G1_TASK=`cat ${G1}/tasks`
196 G2_TASK=`cat ${G2}/tasks`
259 # echo 0 > /cgroup/test/tasks
265 # move all tasks in /cgroup/test to /cgroup
275 Out-of-memory caused by memcg's limit will kill tasks under
279 In this case, panic_on_oom shouldn't be invoked and tasks
306 #echo $$ >/cgroup/A/tasks
314 #echo "pid of the program running in group A" >/cgroup/B/tasks
335 # echo $$ >/cgroup/A/tasks
|
| D | net_prio.rst | 23 becomes visible at '/sys/fs/cgroup/net_prio'. This group includes all tasks in
24 the system. '/sys/fs/cgroup/net_prio/tasks' lists the tasks in this cgroup.
|
| /Documentation/admin-guide/hw-vuln/ |
| D | core-scheduling.rst | 6 Core scheduling support allows userspace to define groups of tasks that can
8 group of tasks don't trust another), or for performance usecases (some
20 attacks. It allows HT to be turned on safely by ensuring that only tasks in a
35 Using this feature, userspace defines groups of tasks that can be co-scheduled
37 tasks that are not in the same group never run simultaneously on a core, while
42 well as admission and removal of tasks from created groups::
67 will be performed for all tasks in the task group of ``pid``.
77 Building hierarchies of tasks
87 Transferring a cookie between the current and other tasks is possible using
91 scheduling group and share it with already running tasks.
[all …]
|
| /Documentation/scheduler/ |
| D | sched-design-CFS.rst | 23 1/nr_running speed. For example: if there are 2 tasks running, then it runs
30 is its actual runtime normalized to the total number of running tasks.
41 Small detail: on "ideal" hardware, at any time all tasks would have the same
42 p->se.vruntime value --- i.e., tasks would execute simultaneously and no task
48 up CPU time between runnable tasks as close to "ideal multitasking hardware" as
66 increasing value tracking the smallest vruntime among all tasks in the
71 The total number of running tasks in the runqueue is accounted through the
72 rq->cfs.load value, which is the sum of the weights of the tasks queued on the
75 CFS maintains a time-ordered rbtree, where all runnable tasks are sorted by the
77 As the system progresses forwards, the executed tasks are put into the tree
[all …]
|
| D | sched-eevdf.rst | 14 runnable tasks with the same priority. To do so, it assigns a virtual run
18 has exceeded its portion. EEVDF picks tasks with lag greater or equal to
21 allows latency-sensitive tasks with shorter time slices to be prioritized,
25 tasks; but at the time of writing EEVDF uses a "decaying" mechanism based
26 on virtual run time (VRT). This prevents tasks from exploiting the system
29 lag to decay over VRT. Hence, long-sleeping tasks eventually have their lag
30 reset. Finally, tasks can preempt others if their VD is earlier, and tasks
|
| 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-util-clamp.rst | 12 of tasks. It was introduced in v5.3 release. The CGroup support was merged in
16 performance requirements and restrictions of the tasks, thus it helps the
35 One can tell the system (scheduler) that some tasks require a minimum
37 can tell the system that some tasks should be restricted from consuming too
45 dropped. It can also dynamically 'prime' up these tasks if it knows in the
56 Another example is in Android where tasks are classified as background,
58 resources background tasks are consuming by capping the performance point they
59 can run at. This constraint helps reserve resources for important tasks, like
63 background tasks to stay on the little cores which will ensure that:
65 1. The big cores are free to run top-app tasks immediately. top-app
[all …]
|
| D | sched-rt-group.rst | 14 2.3 Basis for grouping tasks
44 multiple groups of real-time 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 real-time tasks have explicitly allocated the CPU time they need to perform
74 their tasks, buffer underruns in the graphics or audio can be eliminated.
95 period_us for the real-time tasks. Even without CONFIG_RT_GROUP_SCHED enabled,
112 SCHED_OTHER (non-RT tasks). These defaults were chosen so that a run-away
113 real-time tasks will not lock up the machine but leave a little time to recover
122 bandwidth to the group before it will accept real-time tasks. Therefore you will
[all …]
|
| D | schedutil.rst | 15 individual tasks to task-group slices to CPU runqueues. As the basis for this
28 is key, since it gives the ability to recompose the averages when tasks move
31 Note that blocked tasks still contribute to the aggregates (task-group slices
96 Because periodic tasks have their averages decayed while they sleep, even
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.
147 XXX: deadline tasks (Sporadic Task Model) allows us to calculate a hard f_min
165 suppose we have a CPU saturated with 4 tasks, then when we migrate a task
|
| D | sched-debug.rst | 22 Automatic NUMA balancing scans tasks address space and unmaps pages to
37 rate, the more quickly a tasks memory is migrated to a local node if the
43 tasks virtual memory. It effectively controls the maximum scanning
50 tasks virtual memory. It effectively controls the minimum scanning
|
| D | sched-ext.rst | 12 together, as tasks aren't tied to specific CPUs at the time of wakeup.
55 ``SCHED_EXT`` tasks are scheduled by sched_ext.
58 set in ``ops->flags``, only tasks with the ``SCHED_EXT`` policy are scheduled
59 by sched_ext, while tasks with ``SCHED_NORMAL``, ``SCHED_BATCH`` and
63 detection of any internal error including stalled runnable tasks aborts the
64 BPF scheduler and reverts all tasks back to CFS.
176 * SCHED_BATCH tasks should use sched_ext.
266 ``ops.dispatch_max_batch`` pending tasks.
270 locks held. ``scx_bpf_consume()`` flushes the pending dispatched tasks
273 4. After ``ops.dispatch()`` returns, if there are tasks in the local DSQ,
[all …]
|
| /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
19 The tasks that have PF_NOFREEZE unset (all user space tasks and some kernel
31 wakes up all the kernel threads. All freezable tasks must react to that by
38 tasks are generally frozen before kernel threads.
72 has initiated a freezing operation, the freezing of tasks will fail and the
79 order to wake up each frozen task. Then, the tasks that have been frozen leave
83 Rationale behind the functions dealing with freezing and thawing of tasks
87 - freezes only userspace tasks
[all …]
|
| /Documentation/livepatch/ |
| D | livepatch.rst | 85 transition state where tasks are converging to the patched state.
87 sequence occurs when a patch is disabled, except the tasks converge from
91 interrupts. The same is true for forked tasks: the child inherits the
95 safe to patch tasks:
98 tasks. If no affected functions are on the stack of a given task,
100 the tasks on the first try. Otherwise it'll keep trying
108 a) Patching I/O-bound user tasks which are sleeping on an affected
111 b) Patching CPU-bound user tasks. If the task is highly CPU-bound
115 3. For idle "swapper" tasks, since they don't ever exit the kernel, they
122 the second approach. It's highly likely that some tasks may still be
[all …]
|
| /Documentation/locking/ |
| D | futex-requeue-pi.rst | 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
|
| /Documentation/RCU/ |
| D | stallwarn.rst | 118 The RCU, RCU-sched, RCU-tasks, and RCU-tasks-trace implementations have
209 This boot/sysfs parameter controls the RCU-tasks and
210 RCU-tasks-trace stall warning intervals. A value of zero or less
211 suppresses RCU-tasks stall warnings. A positive value sets the
212 stall-warning interval in seconds. An RCU-tasks stall warning
215 INFO: rcu_tasks detected stalls on tasks:
218 task stalling the current RCU-tasks grace period.
220 An RCU-tasks-trace stall warning starts (and continues) similarly:
222 INFO: rcu_tasks_trace detected stalls on tasks
228 For non-RCU-tasks flavors of RCU, when a CPU detects that some other
[all …]
|
| /Documentation/arch/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
|
| /Documentation/sound/designs/ |
| D | compress-accel.rst | 12 tasks for user space such as sample rate converters, compressed
16 is able to handle "tasks" that are not bound to real-time operations
24 - serialization of multiple tasks for user space to allow multiple
52 For the buffering parameters, the fragments means a limit of allocated tasks
99 tasks.
115 If the multiple tasks require a state handling (e.g. resampling operation),
123 tasks.
|
| /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 …]
|
| /Documentation/driver-api/pm/ |
| D | notifiers.rst | 30 The system is going to hibernate, tasks will be frozen immediately. This
38 executed and tasks have been thawed.
47 callbacks have been executed and tasks have been thawed.
54 resume callbacks have been executed and tasks have been thawed.
|
| /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
|
12345678910