Home
last modified time | relevance | path

Searched refs:tasks (Results 1 – 200 of 201) sorted by relevance

12

/linux-4.4.14/Documentation/cgroups/
Dfreezer-subsystem.txt2 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 …]
Dcpuacct.txt4 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.
Dcgroups.txt41 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 …]
Dhugetlb.txt16 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.
23 # echo $$ > g1/tasks
Dmemcg_test.txt160 /bin/echo $pid >$2/tasks 2>/dev/null
167 G1_TASK=`cat ${G1}/tasks`
168 G2_TASK=`cat ${G2}/tasks`
216 # echo 0 > /cgroup/test/tasks
219 # move all tasks in /cgroup/test to /cgroup
227 Out-of-memory caused by memcg's limit will kill tasks under
230 In this case, panic_on_oom shouldn't be invoked and tasks
249 #echo $$ >/cgroup/A/tasks
255 #echo "pid of the program running in group A" >/cgroup/B/tasks
271 # echo $$ >/cgroup/A/tasks
Dcpusets.txt41 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 …]
D00-INDEX8 - CPU Accounting Controller; account CPU usage for groups of tasks.
10 - documents the cpusets feature; assign CPUs and Mem to a set of tasks.
Dnet_prio.txt22 becomes visible at '/sys/fs/cgroup/net_prio'. This group includes all tasks in
23 the system. '/sys/fs/cgroup/net_prio/tasks' lists the tasks in this cgroup.
Dunified-hierarchy.txt19 3-2. No internal tasks
183 3-2. No internal tasks
186 tasks belonging to the parent cgroup and its children cgroups. This
191 The cpu controller considers tasks and cgroups as equivalents and maps
194 and the number of internal tasks fluctuates - the ratios constantly
198 available for tasks.
201 cgroup to host the tasks. The hidden leaf has its own copies of all
203 over internal tasks, it's with serious drawbacks. It always adds an
208 happens between internal tasks and child cgroups and the behavior is
214 Multiple controllers struggle with internal tasks and came up with
[all …]
Dpids.txt8 new tasks from being fork()'d or clone()'d after a certain limit is reached.
13 the number of tasks in a cgroup.
18 In order to use the `pids` controller, set the maximum number of tasks in
Dmemory.txt21 The memory controller isolates the memory behaviour of a group of tasks
57 tasks # attach a task(thread) and show list of threads
185 This means swapped-in pages may contain pages for other tasks than a task
285 cannot be set if the cgroup have children, or if there are already tasks in the
369 # echo $$ > /sys/fs/cgroup/memory/0/tasks
446 tasks have migrated away from it. (because we charge against pages, not
447 against tasks.)
609 limit, the reclaim algorithm reclaims from the tasks in the ancestor and the
758 If OOM-killer is disabled, tasks under cgroup will hang/sleep
764 * kill some tasks.
[all …]
Dblkio-controller.txt52 echo $! > /sys/fs/cgroup/blkio/test1/tasks
53 cat /sys/fs/cgroup/blkio/test1/tasks
56 echo $! > /sys/fs/cgroup/blkio/test2/tasks
57 cat /sys/fs/cgroup/blkio/test2/tasks
115 directly generated by tasks in that cgroup.
180 deciding how much weight tasks in the given cgroup has while
/linux-4.4.14/samples/bpf/
Dtracex2_user.c75 static struct task tasks[1024]; in print_hist() local
83 if (memcmp(&tasks[i], &next_key, SIZE) == 0) in print_hist()
86 memcpy(&tasks[task_cnt++], &next_key, SIZE); in print_hist()
92 (__u32) tasks[i].pid_tgid, in print_hist()
93 tasks[i].comm, in print_hist()
94 (__u32) tasks[i].uid_gid); in print_hist()
95 print_hist_for_pid(fd, &tasks[i]); in print_hist()
Dtest_maps.c186 static void run_parallel(int tasks, void (*fn)(int i, void *data), void *data) in run_parallel() argument
188 pid_t pid[tasks]; in run_parallel()
191 for (i = 0; i < tasks; i++) { in run_parallel()
201 for (i = 0; i < tasks; i++) { in run_parallel()
/linux-4.4.14/Documentation/scheduler/
Dsched-design-CFS.txt18 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 …]
Dsched-deadline.txt40 that makes it possible to isolate the behavior of tasks between each other.
47 "deadline", to schedule tasks. A SCHED_DEADLINE task should receive
59 Summing up, the CBS[2,3] algorithm assigns scheduling deadlines to tasks so
61 interference between different tasks (bandwidth isolation), while the EDF[1]
63 to be executed next. Thanks to this feature, tasks that do not strictly comply
68 tasks in the following way:
130 suited for periodic or sporadic real-time tasks that need guarantees on their
158 WCET_i/P_i over all the real-time tasks in the system. When considering
159 multiple real-time tasks, the parameters of the i-th task are indicated
162 non- real-time tasks by real-time tasks.
[all …]
Dsched-rt-group.txt14 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 …]
Dsched-nice-design.txt5 pestered us to make nice +19 tasks use up much less CPU time.
35 So that if someone wanted to really renice tasks, +19 would give a much
74 and another task with +2, the CPU split between the two tasks would
90 support: with the new scheduler nice +19 tasks get a HZ-independent
96 tasks, regardless of their absolute nice levels. So on the new
Dsched-domains.txt11 CPUs will never be given tasks to run unless the CPUs allowed mask is
26 out of balance are tasks moved between groups.
45 CPU's runqueue and the newly found busiest one and starts moving tasks from it
46 to our runqueue. The exact number of tasks amounts to an imbalance previously
Dsched-stats.txt51 7) sum of all time spent running by tasks on this processor (in jiffies)
52 8) sum of all time spent waiting to run by tasks on this processor (in
75 more tasks and failed, when the cpu was idle
92 more tasks and failed, when the cpu was busy
108 tasks and failed, when the cpu was just becoming idle
Dcompletion.txt50 providing the wait queue to place tasks on for waiting and the flag for
78 enqueued tasks could get "lost" - use reinit_completion() in that case.
183 designated tasks state and will return -ERESTARTSYS if it is interrupted or
Dsched-bwc.txt13 group exceeds this limit (for that period), the tasks belonging to its
/linux-4.4.14/drivers/gpu/drm/
Ddrm_flip_work.c114 struct list_head tasks; in flip_worker() local
120 INIT_LIST_HEAD(&tasks); in flip_worker()
122 list_splice_tail(&work->commited, &tasks); in flip_worker()
126 if (list_empty(&tasks)) in flip_worker()
129 list_for_each_entry_safe(task, tmp, &tasks, node) { in flip_worker()
/linux-4.4.14/Documentation/power/
Dfreezing-of-tasks.txt1 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 …]
Dnotifiers.txt18 PM_HIBERNATION_PREPARE The system is going to hibernate, tasks will be frozen
26 been executed and tasks have been thawed.
34 and tasks have been thawed.
40 executed and tasks have been thawed.
Dinterface.txt30 tasks, wait for 5 seconds, unfreeze tasks and enable nonboot CPUs. If it is
32 to disable nonboot CPUs and freeze tasks, shrink memory, suspend devices, wait
33 for 5 seconds, resume devices, unfreeze tasks and enable nonboot CPUs. Then,
Dsuspend-and-cpuhotplug.txt22 |tasks | | cpus | | | | cpus | |tasks|
42 Freeze tasks
97 * thaw tasks
148 argument. But during suspend, since the tasks are already frozen by the time
254 tasks could have been frozen by an out-of-band event such as a suspend
270 * Now the freezer continues and tries to freeze the remaining tasks. But
272 the cpu online hotplug task and hence freezing of tasks fails.
D00-INDEX13 freezing-of-tasks.txt
Dcharger-manager.txt33 monitoring the battery health and tasks, and user processes that are
42 requires tasks other than cm_suspend_again, it may implement its own
100 If there are no other devices or tasks that want to use suspend_again
Dswsusp.txt162 Q: What is the freezing of tasks and why are we using it?
164 A: The freezing of tasks is a mechanism by which user space processes and some
166 architectures). See freezing-of-tasks.txt for details.
Dbasic-pm-debugging.txt104 that there is a problem with the tasks freezer subsystem that should be
Ddevices.txt276 various phases always run after tasks have been frozen and before they are
473 callbacks. These phases always run after tasks have been frozen and memory has
670 management notifiers that are called before tasks are frozen and after they have
Dpci.txt144 methods" that may be executed by the kernel to perform specific tasks, such as
385 low-power state. The driver ought to leave these tasks to the PCI subsystem
425 after tasks have been frozen.
/linux-4.4.14/Documentation/kdump/
Dgdbmacros.txt17 set $tasks_off=((size_t)&((struct task_struct *)0)->tasks)
20 set $next_t=(((char *)($init_t->tasks).next) - $tasks_off)
50 set $next_t=(char *)($next_t->tasks.next) - $tasks_off
58 set $tasks_off=((size_t)&((struct task_struct *)0)->tasks)
61 set $next_t=(((char *)($init_t->tasks).next) - $tasks_off)
94 set $next_t=(char *)($next_t->tasks.next) - $tasks_off
103 set $tasks_off=((size_t)&((struct task_struct *)0)->tasks)
106 set $next_t=(((char *)($init_t->tasks).next) - $tasks_off)
124 set $next_t=(char *)($next_t->tasks.next) - $tasks_off
147 set $tasks_off=((size_t)&((struct task_struct *)0)->tasks)
[all …]
/linux-4.4.14/drivers/isdn/hardware/eicon/
Dos_4bri.c154 int tasks = _4bri_is_rev_2_bri_card(a->CardOrdinal) ? 1 : MQ_INSTANCE_COUNT; in diva_4bri_init_card() local
155 int factor = (tasks == 1) ? 1 : 2; in diva_4bri_init_card()
169 bar_length[2], tasks, factor)) in diva_4bri_init_card()
260 if (tasks > 1) { in diva_4bri_init_card()
301 for (i = 0; i < (tasks - 1); i++) { in diva_4bri_init_card()
314 for (i = 0; i < tasks; i++) { in diva_4bri_init_card()
316 adapter_list[i]->xdi_adapter.tasks = tasks; in diva_4bri_init_card()
321 for (i = 0; i < tasks; i++) { in diva_4bri_init_card()
346 for (i = 1; i < (tasks - 1); i++) { in diva_4bri_init_card()
357 for (i = 1; i < (tasks - 1); i++) { in diva_4bri_init_card()
[all …]
Ds_4bri.c52 int factor = (IoAdapter->tasks == 1) ? 1 : 2; in qBri_cpu_trapped()
394 for (i = 0; i < IoAdapter->tasks; ++i) in qBri_ISR()
468 if (!IoAdapter->tasks) { in set_qBri_functions()
469 IoAdapter->tasks = MQ_INSTANCE_COUNT; in set_qBri_functions()
477 if (!IoAdapter->tasks) { in set_qBri2_functions()
478 IoAdapter->tasks = MQ_INSTANCE_COUNT; in set_qBri2_functions()
480 IoAdapter->MemorySize = (IoAdapter->tasks == 1) ? BRI2_MEMORY_SIZE : MQ2_MEMORY_SIZE; in set_qBri2_functions()
497 if (!IoAdapter->tasks) { in prepare_qBri2_functions()
498 IoAdapter->tasks = MQ_INSTANCE_COUNT; in prepare_qBri2_functions()
502 if (IoAdapter->tasks > 1) { in prepare_qBri2_functions()
Dio.h220 dword tasks; member
/linux-4.4.14/tools/perf/scripts/python/
Dsched-migration.py98 def __init__(self, tasks = [0], event = RunqueueEventUnknown()): argument
99 self.tasks = tuple(tasks)
105 if taskState(prev_state) == "R" and next in self.tasks \
106 and prev in self.tasks:
112 next_tasks = list(self.tasks[:])
113 if prev in self.tasks:
125 if old not in self.tasks:
127 next_tasks = [task for task in self.tasks if task != old]
132 if new in self.tasks:
135 next_tasks = self.tasks[:] + tuple([new])
[all …]
/linux-4.4.14/net/irda/
Dirda_device.c58 static hashbin_t *tasks = NULL; variable
71 tasks = hashbin_new(HB_LOCK); in irda_device_init()
72 if (tasks == NULL) { in irda_device_init()
93 hashbin_delete(tasks, (FREE_FUNC) __irda_task_delete); in irda_device_cleanup()
172 hashbin_remove(tasks, (long) task, NULL); in irda_task_delete()
/linux-4.4.14/net/sunrpc/
Dsched.c103 struct list_head *q = &queue->tasks[queue->priority]; in rpc_rotate_queue_owner()
149 q = &queue->tasks[queue_priority]; in __rpc_add_wait_queue_priority()
178 list_add(&task->u.tk_wait.list, &queue->tasks[0]); in __rpc_add_wait_queue()
180 list_add_tail(&task->u.tk_wait.list, &queue->tasks[0]); in __rpc_add_wait_queue()
225 for (i = 0; i < ARRAY_SIZE(queue->tasks); i++) in __rpc_init_priority_wait_queue()
226 INIT_LIST_HEAD(&queue->tasks[i]); in __rpc_init_priority_wait_queue()
470 q = &queue->tasks[queue->priority]; in __rpc_find_next_queued_priority()
488 if (q == &queue->tasks[0]) in __rpc_find_next_queued_priority()
489 q = &queue->tasks[queue->maxpriority]; in __rpc_find_next_queued_priority()
496 } while (q != &queue->tasks[queue->priority]); in __rpc_find_next_queued_priority()
[all …]
/linux-4.4.14/tools/perf/Documentation/
Dperf-timechart.txt48 --tasks-only::
58 Print task info for at least given number of tasks.
63 Highlight tasks (using different color) that run more than given
64 duration or tasks with given name. If number is given it's interpreted
87 --tasks-only::
88 Record only tasks-related events
112 then generate timechart and highlight 'gcc' tasks:
Dperf-bench.txt32 (executing 1000000 pipe operations between two tasks)
120 (executing 1000000 pipe operations between two tasks)
127 (executing 1000 pipe operations between two tasks)
Dperf-inject.txt41 tasks slept. sched_switch contains a callchain where a task slept and
Dperf-sched.txt35 individual CPUs, and the two-letter shortcuts stand for tasks that
Dperf-script-perl.txt133 gives scripts a chance to do setup tasks:
142 processed and gives scripts a chance to do end-of-script tasks, such
Dperf-trace.txt66 Child tasks do not inherit counters.
Dperf-stat.txt47 child tasks do not inherit counters
Dperf-top.txt62 Child tasks do not inherit counters.
Dperf-script-python.txt532 gives scripts a chance to do setup tasks:
540 processed and gives scripts a chance to do end-of-script tasks, such
Dperf-record.txt125 Child tasks do not inherit counters.
/linux-4.4.14/Documentation/x86/x86_64/
Dfake-numa-for-cpusets7 assign them to cpusets and their attached tasks. This is a way of limiting the
8 amount of system memory that are available to a certain class of tasks.
49 You can now assign tasks to these cpusets to limit the memory resources
52 [root@xroads /exampleset/ddset]# echo $$ > tasks
64 This allows for coarse memory management for the tasks you assign to particular
66 interesting combinations of use-cases for various classes of tasks for your
/linux-4.4.14/Documentation/
Dfutex-requeue-pi.txt4 Requeueing of tasks from a non-PI futex to a PI futex requires
16 pthread_cond_broadcast() must resort to waking all the tasks waiting
46 Once pthread_cond_broadcast() requeues the tasks, the cond->mutex
53 be able to requeue tasks to PI futexes. This support implies that
112 possibly wake the waiting tasks. Internally, this system call is
117 nr_wake+nr_requeue tasks to the PI futex, calling
125 requeue up to nr_wake + nr_requeue tasks. It will wake only as many
126 tasks as it can acquire the lock for, which in the majority of cases
Dpadata.txt5 parallel on multiple CPUs while retaining the ordering of tasks. It was
12 overall control of how tasks are to be run:
128 true parallelism is achieved by submitting multiple tasks. Despite the
150 pains to ensure that tasks are completed in the order in which they were
158 This function will busy-wait while any remaining tasks are completed, so it
Dkernel-per-CPU-kthreads.txt13 o Documentation/cgroups: Using cgroups to bind tasks to sets of CPUs.
15 o man taskset: Using the taskset command to bind tasks to sets
19 call to bind tasks to sets of CPUs.
83 from being initiated from tasks that might run on the CPU to
90 from being initiated from tasks that might run on the CPU to
97 from being initiated from tasks that might run on the CPU to
Dsysrq.txt28 256 = 0x100 - allow nicing of all RT tasks
97 'n' - Used to make RT tasks nice-able
111 't' - Will dump a list of current tasks and their information to your
119 'w' - Dumps tasks that are in uninterruptable (blocked) state.
Dpi-futex.txt31 Firstly, sharing locks between multiple tasks is a common programming
44 design with multiple tasks (with multiple priority levels) sharing
Dcpu-load.txt26 moment and increments the counter that corresponds to this tasks
Dlockup-watchdogs.txt10 details), without giving other tasks a chance to run. The current
Drtc.txt137 other tasks, because of its greater functionality.
192 state until it's time to execute some scheduled tasks.
Dpreempt-locking.txt45 Remember, the kernel does not save FPU state except for user tasks. Therefore,
Drpmsg.txt21 multimedia tasks from the main application processor.
24 sensors, drive random hardware blocks, or just perform background tasks
Dcpu-hotplug.txt248 CPU is being offlined while tasks are frozen due to a suspend operation in
258 CPU_DEAD (or CPU_DEAD_FROZEN if tasks are frozen due to a suspend while the
Dvgaarbiter.txt13 the legacy VGA arbitration task (besides other bus management tasks) when more
Dkmemleak.txt47 stack=off - disable the tasks stacks scanning
Drobust-futexes.txt181 So there is virtually zero overhead for tasks not using robust futexes,
Dhwspinlock.txt20 on OMAP4, cpu-intensive multimedia tasks are offloaded by the host to the
Dvme_api.txt247 reused for repetitive tasks:
Dinitrd.txt281 8) now the system is bootable and additional installation tasks can be
Dworkqueue.txt266 Ignoring all other tasks, works and processing overhead, and assuming
D00-INDEX199 - info on requeueing of tasks from a non-PI futex to a PI futex
Dxillybus.txt58 One of the daunting tasks in FPGA design is communicating with a fullblown
Dkernel-parameters.txt1664 tasks in the system -- can cause problems and
1907 tasks allows some CPUs to go into dyntick-idle
3251 Set task-shuffle interval (s). Shuffling tasks
Ddevices.txt2712 4 = /dev/vx/task Volume tasks access node
2713 5 = /dev/vx/taskmon Volume tasks monitor daemon
/linux-4.4.14/ipc/
Dsem.c1092 struct list_head tasks; in freeary() local
1107 INIT_LIST_HEAD(&tasks); in freeary()
1110 wake_up_sem_queue_prepare(&tasks, q, -EIDRM); in freeary()
1115 wake_up_sem_queue_prepare(&tasks, q, -EIDRM); in freeary()
1121 wake_up_sem_queue_prepare(&tasks, q, -EIDRM); in freeary()
1125 wake_up_sem_queue_prepare(&tasks, q, -EIDRM); in freeary()
1134 wake_up_sem_queue_do(&tasks); in freeary()
1274 struct list_head tasks; in semctl_setval() local
1287 INIT_LIST_HEAD(&tasks); in semctl_setval()
1331 do_smart_update(sma, NULL, 0, 0, &tasks); in semctl_setval()
[all …]
/linux-4.4.14/scripts/gdb/linux/
Dcpus.py16 from linux import tasks, utils
30 return tasks.get_thread_info(tasks.get_task_by_pid(tid))['cpu']
/linux-4.4.14/Documentation/namespaces/
Dcompatibility-list.txt4 may have when creating tasks living in different namespaces.
7 occur when tasks share some namespace (the columns) while living
22 In both cases, tasks shouldn't try exposing this ID to some
/linux-4.4.14/Documentation/RCU/
Dstallwarn.txt49 This boot/sysfs parameter controls the RCU-tasks stall warning
50 interval. A value of zero or less suppresses RCU-tasks stall
52 in jiffies. An RCU-tasks stall warning starts wtih the line:
54 INFO: rcu_tasks detected stalls on tasks:
57 task stalling the current RCU-tasks grace period.
59 For non-RCU-tasks flavors of RCU, when a CPU detects that it is stalling,
75 INFO: rcu_bh_state detected stalls on CPUs/tasks: { 3 5 } (detected by 2, 2502 jiffies)
80 PREEMPT_RCU builds can be stalled by tasks as well as by CPUs,
81 and that the tasks will be indicated by PID, for example, "P3421".
83 CPUs -and- tasks, in which case the offending CPUs and tasks will all
[all …]
Dtrace.txt350 of the blocked-tasks lists. A "G" preceding the ">"
361 does not hold, so that "..>." indicates that no tasks
363 inconvenience from blocked tasks. CONFIG_TREE_RCU
428 0:3 tasks=.... kt=W ntb=0 neb=0 nnb=0 j=c864 bt=c894
430 4:7 tasks=.... kt=W ntb=0 neb=0 nnb=0 j=c864 bt=c894
441 o "tasks=TNEB" gives the state of the various segments of the
444 "T" This indicates that there are some tasks that blocked
448 "N" This indicates that some of the blocked tasks are preventing
452 "E" This indicates that some of the blocked tasks are preventing
455 "B" This indicates that some of the blocked tasks are in
[all …]
DwhatisRCU.txt348 c. RCU applied to scheduler and interrupt/NMI-handler tasks.
654 than just leaving all tasks running on the last CPU, but when I said
957 the context of special tasks. In this case, in step 4
973 approach where tasks in RCU read-side critical sections
974 cannot be blocked by tasks executing synchronize_rcu().
Drcubarrier.txt172 Lines 7-50 stop all the kernel tasks associated with the rcutorture
Dtorture.txt188 "tasks": voluntary context switch and call_rcu_tasks(),
Dchecklist.txt42 information relating to itself that other tasks can read, there
DRTFP.txt20 However, Linux has long-lived tasks, so more is needed.
/linux-4.4.14/drivers/dma/bestcomm/
DKconfig29 This option enables the support for the FEC tasks.
35 This option enables the support for the GenBD tasks.
/linux-4.4.14/Documentation/devicetree/bindings/soc/mediatek/
Dscpsys.txt5 related tasks in the system. The tasks include thermal measurement, dynamic
/linux-4.4.14/Documentation/accounting/
Dcgroupstats.txt14 Statistics about the state of all the tasks in the cgroup is returned to
18 about tasks blocked on I/O. If CONFIG_TASK_DELAY_ACCT is disabled, this
Ddelay-accounting.txt21 important tasks could be a trigger for raising its corresponding priority.
24 delay statistics aggregated for all tasks (or threads) belonging to a
Dtaskstats.txt22 tasks that share an mm_struct i.e. the traditional Unix process. Despite the
32 statistics for all tasks of the process (if tgid is specified).
34 To obtain statistics for tasks which are exiting, the userspace listener
/linux-4.4.14/include/linux/
Dinit_task.h76 .tasks = { \
214 .tasks = LIST_HEAD_INIT(tsk.tasks), \
Dpid.h62 struct hlist_head tasks[PIDTYPE_MAX]; member
179 &(pid)->tasks[type], pids[type].node) {
Dcgroup-defs.h171 struct list_head tasks; member
Dsched.h1438 struct list_head tasks; member
2657 list_empty(&init_task.tasks)
2660 list_entry_rcu((p)->tasks.next, struct task_struct, tasks)
/linux-4.4.14/Documentation/ia64/
Dmca.txt60 tasks. The only way to do that on ia64 is to call the unwinder,
66 knows how to start unwinding it. The tasks that received an MCA or
68 tasks. But (and its a big but), the cpus that received the MCA
72 tasks are on a cpu and which are not. Hence each slave cpu that
91 stacks meant separate "tasks" for the MCA/INIT handlers.
99 time. The OS monarch prints the state of all tasks and returns, after
162 How do we get a backtrace on the tasks that were running when MCA/INIT
177 How do we identify the tasks that were running when MCA/INIT was
183 To help distinguish between the handler and the original tasks,
/linux-4.4.14/tools/testing/selftests/rcutorture/configs/rcu/
DTASKS02.boot1 rcutorture.torture_type=tasks
DTASKS01.boot1 rcutorture.torture_type=tasks
DTASKS03.boot1 rcutorture.torture_type=tasks
/linux-4.4.14/scripts/gdb/
Dvmlinux-gdb.py29 import linux.tasks
/linux-4.4.14/Documentation/x86/
Dearlyprintk.txt126 …tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) saK show-backtrace-all-active-cpus(L) show-memo…
/linux-4.4.14/kernel/
Dpid.c332 INIT_HLIST_HEAD(&pid->tasks[type]); in alloc_pid()
392 hlist_add_head_rcu(&link->node, &link->pid->tasks[type]); in attach_pid()
409 if (!hlist_empty(&pid->tasks[tmp])) in __change_pid()
440 first = rcu_dereference_check(hlist_first_rcu(&pid->tasks[type]), in pid_task()
Dcgroup.c593 .tasks = LIST_HEAD_INIT(init_css_set.tasks),
610 return !list_empty(&cset->tasks) || !list_empty(&cset->mg_tasks); in css_set_populated()
727 &to_cset->tasks); in css_set_move_task()
1038 INIT_LIST_HEAD(&cset->tasks); in find_css_set()
1864 list_add_tail(&p->cg_list, &cset->tasks); in cgroup_enable_task_cg_lists()
2446 list_splice_tail_init(&cset->mg_tasks, &cset->tasks); in cgroup_taskset_migrate()
2954 list_for_each_entry_safe(task, ntask, &src_cset->tasks, cg_list) in cgroup_update_dfl_csses()
3908 if (!list_empty(&cset->tasks)) in css_task_iter_advance_css_set()
3909 it->task_pos = cset->tasks.next; in css_task_iter_advance_css_set()
3913 it->tasks_head = &cset->tasks; in css_task_iter_advance_css_set()
[all …]
Dexit.c72 list_del_rcu(&p->tasks); in __unhash_process()
1496 (!wo->wo_pid || hlist_empty(&wo->wo_pid->tasks[wo->wo_type]))) in do_wait()
Dfork.c1589 list_add_tail_rcu(&p->tasks, &init_task.tasks); in copy_process()
/linux-4.4.14/drivers/oprofile/
Dbuffer_sync.c60 list_add(&task->tasks, &dying_tasks); in task_free_notify()
447 list_for_each_entry_safe(task, ttask, &local_dead_tasks, tasks) { in process_task_mortuary()
448 list_del(&task->tasks); in process_task_mortuary()
/linux-4.4.14/Documentation/devicetree/bindings/timer/
Dstericsson-u300-apptimer.txt9 adopted for EPOC/Symbian with two specific IRQs for these tasks,
/linux-4.4.14/tools/perf/
Dbuiltin-sched.c130 struct task_desc **tasks; member
364 sched->tasks = realloc(sched->tasks, sched->nr_tasks * sizeof(struct task_desc *)); in register_pid()
365 BUG_ON(!sched->tasks); in register_pid()
366 sched->tasks[task->nr] = task; in register_pid()
381 task = sched->tasks[i]; in print_task_traces()
393 task1 = sched->tasks[i]; in add_cross_task_wakeups()
397 task2 = sched->tasks[j]; in add_cross_task_wakeups()
565 parms->task = task = sched->tasks[i]; in create_tasks()
588 task = sched->tasks[i]; in wait_for_tasks()
601 task = sched->tasks[i]; in wait_for_tasks()
[all …]
Ddesign.txt200 events on descendant tasks as well as the task specified. This only
242 pid < 0: all tasks are counted (per cpu counters)
254 their own tasks.
/linux-4.4.14/sound/pci/cs46xx/
Ddsp_spos.c564 snd_iprintf(buffer,"\n%04x %s:\n",ins->tasks[i].address,ins->tasks[i].task_name); in cs46xx_dsp_proc_task_tree_read()
566 for (col = 0,j = 0;j < ins->tasks[i].size; j++,col++) { in cs46xx_dsp_proc_task_tree_read()
572 val = readl(dst + (ins->tasks[i].address + j) * sizeof(u32)); in cs46xx_dsp_proc_task_tree_read()
1022 strcpy(ins->tasks[ins->ntask].task_name, name); in _map_task_tree()
1024 strcpy(ins->tasks[ins->ntask].task_name, "(NULL)"); in _map_task_tree()
1025 ins->tasks[ins->ntask].address = dest; in _map_task_tree()
1026 ins->tasks[ins->ntask].size = size; in _map_task_tree()
1029 ins->tasks[ins->ntask].index = ins->ntask; in _map_task_tree()
1030 desc = (ins->tasks + ins->ntask); in _map_task_tree()
2015 struct dsp_task_descriptor *t = &ins->tasks[i]; in cs46xx_dsp_resume()
Dcs46xx_dsp_spos.h194 struct dsp_task_descriptor tasks[DSP_MAX_TASK_DESC]; member
/linux-4.4.14/kernel/debug/kdb/
Dkdb_cmds26 defcmd dumpcpu "" "Same as dumpall but only tasks on cpus"
/linux-4.4.14/Documentation/timers/
DNO_HZ.txt36 right approach, for example, in heavy workloads with lots of tasks
41 will frequently be multiple runnable tasks per CPU. In these cases,
124 online to handle timekeeping tasks in order to ensure that system
174 This might in turn perturb load-balancing of real-time tasks.
292 of low-priority SCHED_OTHER tasks. In this case, the CPU is
299 tasks, even though these interrupts are unnecessary.
301 And even when there are multiple runnable tasks on a given CPU,
317 of OS jitter, including interrupts and system-utility tasks
319 interrupts and tasks to particular CPUs.
/linux-4.4.14/drivers/gpu/drm/amd/amdgpu/
Dsmu_ucode_xfer_cz.h102 SMU_Task tasks[1]; member
Dcz_smc.c508 struct SMU_Task *task = &toc->tasks[priv->toc_entry_used_count++]; in cz_smu_populate_single_ucode_load_task()
537 struct SMU_Task *task = &toc->tasks[priv->toc_entry_used_count++]; in cz_smu_populate_single_scratch_task()
/linux-4.4.14/Documentation/security/
Dcredentials.txt75 objects within the system. Processes/tasks are the obvious exception:
78 Objects other than tasks may under some circumstances also be subjects.
102 signalling and tracing tasks.
156 that object, with tasks being slightly different in some cases.
162 These are additional credentials used by tasks only. Usually, an
164 will be used as the objective. For tasks, it should be noted that this is
174 These are only carried by tasks. They indicate superior capabilities
195 These are only carried by tasks. These govern the way the above
202 These are only carried by tasks. They carry and cache security tokens
DSmack.txt340 On Smack files of all types, IPC, and tasks can be objects.
502 Process objects reflect tasks on the system and the Smack label used to access
507 tasks with identical Smack labels and requires no access checks.
602 can only be set by privileged tasks, but any task can read them for their own
/linux-4.4.14/Documentation/locking/
Drt-mutex.txt25 This approach allows us to shorten the block of high-prio tasks on
71 uninterrupted workflow of high-prio tasks which repeatedly
Dmutex-design.txt57 while the lock owner is running and there are no other tasks ready
113 locks and tasks (and only those tasks).
Dww-mutex-design.txt36 The older tasks waits until it can acquire the contended lock. The younger tasks
Dlglock.txt134 does not change the tasks state while sleeping [6].
Dlockdep-design.txt187 a very unlikely constellation of tasks, irq-contexts and timings to
Drt-mutex-design.txt435 prevents new tasks from completing the blocking on a mutex that is owned by this
702 especially on SCHED_OTHER tasks, the current process can be the
/linux-4.4.14/tools/perf/util/
Devent.c418 DIR *tasks; in __event__synthesize_thread() local
442 tasks = opendir(filename); in __event__synthesize_thread()
443 if (tasks == NULL) { in __event__synthesize_thread()
448 while (!readdir_r(tasks, &dirent, &next) && next) { in __event__synthesize_thread()
480 closedir(tasks); in __event__synthesize_thread()
/linux-4.4.14/tools/testing/ktest/examples/
DREADME1 This directory contains example configs to use ktest for various tasks.
/linux-4.4.14/Documentation/acpi/
Dscan_handlers.txt30 Those additional configuration tasks usually depend on the type of the hardware
54 for carrying out any additional configuration tasks related to it. It also will
/linux-4.4.14/Documentation/devicetree/bindings/remoteproc/
Dwkup_m3_rproc.txt5 (commonly referred to as Wakeup M3 or CM3) to help with various low power tasks
/linux-4.4.14/Documentation/vm/
Dnuma_memory_policy.txt83 VMA policies are shared between all tasks that share a virtual address
103 mapped shared into one or more tasks' distinct address spaces. An
108 apply directly to the shared object. Thus, all tasks that attach to the
131 Thus, different tasks that attach to a shared memory segment can have
133 can be seen by examining the /proc/<pid>/numa_maps of tasks sharing
357 true for shared policies on shared memory regions shared by tasks running
444 The interaction of memory policies and cpusets can be problematic when tasks
447 any of the tasks install shared policy on the region, only nodes whose
Dhwpoison.txt140 echo `jobs -p` > /sys/fs/cgroup/mem/hwpoison/tasks
Dunevictable-lru.txt118 tasks are changing the "evictability" state of the page.
142 are unevictable, the evictable portion of the working set of the tasks in
144 the control group to thrash or to OOM-kill tasks.
Dnuma104 Thus, under sufficient imbalance, tasks can migrate between nodes, remote
/linux-4.4.14/Documentation/netlabel/
Dintroduction.txt20 engine will handle those tasks as well. Other kernel subsystems should
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-power58 the kernel to disable nonboot CPUs and freeze tasks, wait for 5
59 seconds, unfreeze tasks and enable nonboot CPUs. If it is in
61 the kernel to disable nonboot CPUs and freeze tasks, shrink
63 unfreeze tasks and enable nonboot CPUs. Then, we are able to
/linux-4.4.14/kernel/time/
DKconfig104 the CPU is running tasks. Typically this requires running a single
137 running non-idle tasks. Because the underlying adaptive-tick
/linux-4.4.14/Documentation/block/
Dcfq-iosched.txt152 Internal cgroup nodes (the ones with children) can also have tasks in
155 configure how much proportion the tasks in the cgroup have compared to
159 an implicit leaf child node which hosts all the tasks whose weight is
173 and AB have no child and thus its tasks have no children cgroup to
/linux-4.4.14/include/linux/sunrpc/
Dsched.h183 struct list_head tasks[RPC_NR_PRIORITY]; /* task queue for each priority level */ member
/linux-4.4.14/Documentation/usb/
Dmtouchusb.txt55 tasks).
/linux-4.4.14/Documentation/sound/alsa/soc/
Dmachine.txt46 of any machine audio tasks that have to be done before or after the codec, DAIs
/linux-4.4.14/Documentation/frv/
Dfeatures.txt274 them to specific tasks).
277 or CLONE_VM'd group of tasks for as long as it exists. However, since the
278 kernel is capable of supporting more tasks than there are possible ID
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/nintendo/
Dgamecube.txt48 audio related tasks.
Dwii.txt59 audio related tasks.
/linux-4.4.14/Documentation/prctl/
Dno_new_privs.txt54 available to unprivileged tasks if no_new_privs is set. In principle,
/linux-4.4.14/arch/sh/
DKconfig.debug15 boot for various housekeeping tasks (including calls to read and
/linux-4.4.14/init/
DKconfig427 Export selected statistics for tasks/processes through the
429 statistics are available during the lifetime of tasks/processes as
443 relative to other tasks for cpu, io, rss limits etc.
678 tasks. For example, if one thread at priority 10 and another
956 Provides a way to freeze and unfreeze all tasks in a
986 Memory Nodes and assigning tasks to run only within those sets.
1000 total CPU consumed by the tasks in a cgroup.
1087 tasks.
1101 tasks running within the fair group scheduler. Groups with no limit
1113 schedule realtime tasks for non-root users until you allocate
[all …]
/linux-4.4.14/Documentation/trace/
Dftrace.txt535 Traces all tasks as an average developer would expect.
540 RT tasks (as the current "wakeup" does). This is useful
541 for those interested in wake up timings of RT tasks.
1391 Now for non Real-Time tasks, this can be arbitrary. But tracing
1431 Non Real-Time tasks are not that interesting. A more interesting
1432 trace is to concentrate only on Real-Time tasks.
1440 latency". I stress the point that this is about RT tasks. It is
1441 also important to know the scheduling latency of non-RT tasks,
1442 but the average schedule latency is better for non-RT tasks.
1450 work well with Real-Time tasks. The wakeup_rt tracer was designed
[all …]
/linux-4.4.14/arch/cris/arch-v32/kernel/
Dentry.S348 add.d $r12, $r10 ; R10 = current tasks tss.
367 add.d $r12, $r11 ; Find the new tasks tss.
/linux-4.4.14/kernel/sched/
Dfair.c5545 struct list_head tasks; member
5769 struct list_head *tasks = &env->src_rq->cfs_tasks; in detach_tasks() local
5779 while (!list_empty(tasks)) { in detach_tasks()
5787 p = list_first_entry(tasks, struct task_struct, se.group_node); in detach_tasks()
5813 list_add(&p->se.group_node, &env->tasks); in detach_tasks()
5837 list_move_tail(&p->se.group_node, tasks); in detach_tasks()
5880 struct list_head *tasks = &env->tasks; in attach_tasks() local
5885 while (!list_empty(tasks)) { in attach_tasks()
5886 p = list_first_entry(tasks, struct task_struct, se.group_node); in attach_tasks()
6969 .tasks = LIST_HEAD_INIT(env.tasks), in load_balance()
/linux-4.4.14/Documentation/filesystems/
Dfiles.txt11 table between tasks cloned with CLONE_FILES flag. Typically
Dbtrfs.txt266 Other tools for specific tasks:
Dgfs2-glocks.txt13 workqueue) when it releases it in order to ensure any pending tasks
Dproc.txt388 of the individual tasks of a process. In this file you will see a mapping marked
391 as stack by all of those tasks. Hence, for the example above, the task-level
1472 example, is roughly equivalent to allowing the remainder of tasks sharing the
1690 These files provide a method to access a tasks comm value. It also allows for
Dcoda.txt230 which does not block Venus since Venus must attend to other tasks even
/linux-4.4.14/tools/lguest/
Dlguest.txt9 make it useful for specific tasks, and, of course, you are encouraged to fork
/linux-4.4.14/arch/mn10300/
DKconfig133 task's thread struct. This is useful if most tasks on the system
134 don't use the FPU as only those tasks that use it will pass it
/linux-4.4.14/Documentation/scsi/
Dufs.txt124 UFSHCD Routines to perform these tasks are registered with
DChangeLog.sym53c8xx_278 - Forces the max number of tasks per LUN to at least 64.
Dlibsas.txt22 phy/OOB management, and vendor specific tasks and generates
25 The SAS Layer does most SAS tasks as outlined in the SAS 1.1
Dsym53c8xx_2.txt29 8.8 Abort all tasks of all logical units of a target
387 8.8 Abort all tasks of all logical units of a target
DChangeLog.ncr53c8xx254 - Cleanup of the SCSI tasks management:
Dncr53c8xx.txt29 8.10 Abort all tasks of all logical units of a target
547 8.10 Abort all tasks of all logical units of a target
/linux-4.4.14/Documentation/sysctl/
Dkernel.txt329 The upper bound on the number of tasks that are checked.
481 Automatic NUMA balancing scans tasks address space and unmaps pages to
496 rate, the more quickly a tasks memory is migrated to a local node if the
502 scan a tasks virtual memory. It effectively controls the maximum scanning
509 scan a tasks virtual memory. It effectively controls the minimum scanning
Dvm.txt577 large systems with thousands of tasks it may not be feasible to dump
/linux-4.4.14/arch/cris/arch-v10/kernel/
Dentry.S308 add.d $r12, $r10 ; r10 = current tasks tss
322 add.d $r12, $r11 ; find the new tasks tss
/linux-4.4.14/Documentation/gpio/
Dsysfs.txt20 standard kernels won't know about. And for some tasks, simple userspace
Ddrivers-on-gpio.txt4 Note that standard kernel drivers exist for common GPIO tasks and will provide
Dgpio-legacy.txt639 standard kernels won't know about. And for some tasks, simple userspace
643 GPIO tasks: "leds-gpio" and "gpio_keys", respectively. Use those
/linux-4.4.14/Documentation/arm/
Dkernel_mode_neon.txt31 kept 'live', and is only preserved and restored when multiple tasks are
/linux-4.4.14/Documentation/target/
Dtcmu-design.txt238 the kernel will abort pending tasks.
242 - The kernel will abort pending tasks after a timeout period.
/linux-4.4.14/drivers/dma/
Dpl330.c481 struct tasklet_struct tasks; member
1625 tasklet_schedule(&pl330->tasks); in pl330_update()
1889 tasklet_init(&pl330->tasks, pl330_dotask, (unsigned long) pl330); in pl330_add()
1917 tasklet_kill(&pl330->tasks); in pl330_del()
/linux-4.4.14/Documentation/networking/
Dnetdev-features.txt14 that relieve an OS of various tasks like generating and checking checksums,
Dcan.txt643 Periodic transmission tasks of CAN frames or a sequence of CAN frames can be
754 TX tasks the unique can_id from the message header may differ from the
/linux-4.4.14/arch/microblaze/
DKconfig220 allocated to user tasks. This can be useful in optimizing the
/linux-4.4.14/lib/
DKconfig.debug698 mode for more than 20 seconds, without giving other tasks a
744 sysctl), without giving other tasks a chance to run.
766 Say Y here to enable the kernel to detect "hung tasks",
796 Say Y here to enable the kernel to panic on "hung tasks",
804 where a hung tasks must be resolved ASAP.
992 arbitrary number of tasks and interrupt contexts) cause a
1000 participant CPUs, tasks and irq-contexts would be needed
/linux-4.4.14/Documentation/fault-injection/
Dfault-injection.txt256 In order to make it easier to accomplish the tasks mentioned above, we can use
/linux-4.4.14/fs/
Dexec.c988 list_replace_rcu(&leader->tasks, &tsk->tasks); in de_thread()
/linux-4.4.14/Documentation/i2c/
Ddev-interface186 3* Some ioctl() calls are for administrative tasks and are handled by
/linux-4.4.14/fs/reiserfs/
DREADME158 the alpha port. Many of these tasks were helped by sponsors other
/linux-4.4.14/arch/arm/kernel/
Dentry-armv.S235 ldr r0, [tsk, #TI_FLAGS] @ get new tasks TI_FLAGS
/linux-4.4.14/kernel/power/
DKconfig17 done, no tasks are frozen for suspend to RAM/standby.
/linux-4.4.14/Documentation/thermal/
Dintel_powerclamp.txt91 for a given "duration", then relinquishes the CPU to other tasks,
/linux-4.4.14/net/
DKconfig40 to tasks depending on whether the task is a compat task or not. To
/linux-4.4.14/arch/arc/
DKconfig376 this for all tasks in system.
/linux-4.4.14/sound/isa/
DKconfig393 coprocessor can do variable tasks like various compression and
/linux-4.4.14/Documentation/fmc/
Dcarrier.txt149 The individual methods perform the following tasks:
/linux-4.4.14/arch/
DKconfig353 Enable tasks to build secure computing environments defined
/linux-4.4.14/Documentation/DocBook/
Dnetworking.xml.db218 API-xprt-wake-pending-tasks
Ddevice-drivers.xml.db258 API-synchronize-rcu-tasks
259 API-rcu-barrier-tasks
/linux-4.4.14/arch/m68k/fpsp040/
Dround.S4 | handle rounding and normalization tasks
/linux-4.4.14/Documentation/filesystems/caching/
Dfscache.txt320 between 0 jiffies and HZ-1 jiffies a variety of tasks took to run. The
Dcachefiles.txt465 between 0 jiffies and HZ-1 jiffies a variety of tasks took to run. The
/linux-4.4.14/arch/ia64/kernel/
Dmca.c1826 INIT_LIST_HEAD(&p->tasks); in format_mca_init_stack()
/linux-4.4.14/Documentation/dmaengine/
Dprovider.txt164 - Used to accelerate XOR intensive tasks, such as RAID5
/linux-4.4.14/Documentation/blockdev/
Dparide.txt194 among other tasks.
/linux-4.4.14/Documentation/filesystems/configfs/
Dconfigfs.txt113 handles that. The group has a set of operations to perform these tasks
/linux-4.4.14/kernel/trace/
DKconfig546 goes into an infinite loop (calling cond_sched() to let other tasks
/linux-4.4.14/arch/powerpc/
DKconfig1013 allocated to user tasks. This can be useful in optimizing the
/linux-4.4.14/drivers/scsi/aic7xxx/
Daic7xxx.reg506 * perform the tasks of accessing a serial eeprom, testing termination
/linux-4.4.14/drivers/scsi/
DKconfig909 you will still be able to use the parallel port for other tasks,
936 you will still be able to use the parallel port for other tasks,
/linux-4.4.14/fs/proc/
Dbase.c1768 return !proc_pid(inode)->tasks[PIDTYPE_PID].first; in proc_inode_is_dead()
/linux-4.4.14/Documentation/video4linux/
Dv4l2-framework.txt210 sort of tasks, but most commonly they handle audio and/or video muxing,
/linux-4.4.14/arch/mips/
DKconfig1623 many ethernet hardware widgets for networking tasks. The processor
/linux-4.4.14/Documentation/s390/
DDebugging390.txt2110 ^-t will show tasks.
/linux-4.4.14/arch/x86/
DKconfig721 accounting. Time spent executing other tasks in parallel with

12