| /Linux-v4.19/tools/testing/selftests/powerpc/benchmarks/ |
| D | context_switch.c | 272 static int processes; variable
278 if (!processes) in mutex_lock()
299 if (!processes) in mutex_unlock()
316 if (!processes) { in futex_setup()
383 { "process", no_argument, &processes, 1 },
456 if (processes) in main()
468 printf("Using %s with ", processes ? "processes" : "threads"); in main()
|
| /Linux-v4.19/Documentation/cgroup-v1/ |
| D | pids.txt | 20 number of processes currently in the cgroup is given by pids.current.
24 be smaller than pids.current, or attaching enough processes to the cgroup such
43 Then we create a hierarchy, set limits and attach processes to it:
56 # ( /bin/echo "Here's some processes for you." | cat )
71 # ( /bin/echo "Here's some processes for you." | cat )
76 processes from being forked at all (note that the shell itself counts towards
|
| D | rdma.txt | 19 set of processes can use. These processes are grouped using RDMA controller.
21 RDMA controller defines two resources which can be limited for processes of a
33 of processes can be limited. Through this controller different rdma
51 of the child processes which shares the address space, rdma resources are
56 deleted after processes migrated. This allow progress migration as well with
|
| D | net_prio.txt | 33 processes in this group and egressing the system on various interfaces. It
40 This command would force any traffic originating from processes belonging to the
|
| /Linux-v4.19/Documentation/admin-guide/LSM/ |
| D | Yama.rst | 16 running state of any of their processes. For example, if one application
18 attach to other running processes (e.g. Firefox, SSH sessions, GPG agent,
42 Firefox's crash handlers, and by Wine for allowing only Wine processes
67 only processes with ``CAP_SYS_PTRACE`` may use ptrace
71 no processes may use ptrace with ``PTRACE_ATTACH`` nor via
|
| /Linux-v4.19/Documentation/power/ |
| D | freezing-of-tasks.txt | 6 The freezing of tasks is a mechanism by which user space processes and some
14 PF_NOFREEZE unset (all user space processes and some kernel threads) are
24 fake signal to all user space processes, and wakes up all the kernel threads.
31 kernel/freezer.c & include/linux/freezer.h). User space processes are generally
38 For user space processes try_to_freeze() is called automatically from the
110 The majority of these are user space processes, but if any of the kernel threads
122 3. The third reason is to prevent user space processes and some kernel threads
152 4. Another reason for freezing tasks is to prevent user space processes from
154 space processes should not notice that such a system-wide operation has occurred
174 space processes:
[all …]
|
| D | basic-pm-debugging.txt | 47 - test the freezing of processes
50 - test the freezing of processes and suspending of devices
53 - test the freezing of processes, suspending of devices and platform
57 - test the freezing of processes, suspending of devices, platform
61 - test the freezing of processes, suspending of devices, platform global
69 /sys/power/pm_test (eg. "devices" to test the freezing of processes and
78 Then, the kernel will try to freeze processes, suspend devices, wait a few
80 parameter), resume devices and thaw processes. If "platform" is written to
|
| /Linux-v4.19/tools/power/pm-graph/config/ |
| D | suspend-x2-proc.cfg | 2 # Proc S3 (Suspend to Mem) x2 test - includes user processes
45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| D | freeze.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| D | standby.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| D | freeze-callgraph.cfg | 46 # Display user processes
47 # graph user processes and cpu usage in the timeline (default: false)
|
| D | freeze-dev.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| D | standby-callgraph.cfg | 46 # Display user processes
47 # graph user processes and cpu usage in the timeline (default: false)
|
| D | suspend-dev.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| D | standby-dev.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| D | suspend-callgraph.cfg | 46 # Display user processes
47 # graph user processes and cpu usage in the timeline (default: false)
|
| D | suspend.cfg | 45 # Display user processes
46 # graph user processes and cpu usage in the timeline (default: false)
|
| /Linux-v4.19/drivers/android/ |
| D | Kconfig | 16 Binder is used in Android for both communication between processes,
21 between said processes.
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 99 cgroup is a mechanism to organize processes hierarchically and
105 processes. A cgroup controller is usually responsible for
112 same cgroup. On creation, all processes are put in the cgroup that
115 existing descendant processes.
120 processes which belong to the cgroups consisting the inclusive
185 Initially, only the root cgroup exists to which all processes belong.
192 "cgroup.procs". When read, it lists the PIDs of all processes which
210 A cgroup which doesn't have any children or live processes can be
212 have any children and is associated only with zombie processes is
239 the threads of a group of processes. By default, all threads of a
[all …]
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | mandatory-locking.txt | 32 processes. File locks are applied using the flock() and fcntl() system calls
41 In a perfect world all processes would use and honour a cooperative, or
123 other processes are permitted to read from that region. If any of these
124 processes attempts to write to the region it will block until the lock is
135 any mandatory locks owned by other processes will be rejected with the
167 Not even root can override a mandatory lock, so runaway processes can wreak
|
| /Linux-v4.19/include/linux/sched/ |
| D | user.h | 17 atomic_t processes; /* How many processes does this user have? */ member
|
| /Linux-v4.19/tools/testing/selftests/android/ion/ |
| D | README | 9 between 2 independent processes.
13 two user space processes, using various heap types.
37 Thus the same kernel buffer is shared among two user space processes using
|
| /Linux-v4.19/Documentation/block/ |
| D | ioprio.txt | 10 processes or process groups, similar to what has been possible with cpu
21 higher priority than any other in the system, processes from this class are
36 IOPRIO_CLASS_IDLE: This is the idle scheduling class, processes running at this
|
| /Linux-v4.19/block/ |
| D | Kconfig.iosched | 30 among all processes in the system. It should provide a fair
88 of the device among all processes according to their weights,
|
| /Linux-v4.19/Documentation/locking/ |
| D | rt-mutex-design.txt | 34 processes, let's call them processes A, B, and C, where A is the highest
65 to understand, let's use the previous example, with processes A, B, and C again.
78 PI chain - The PI chain is an ordered series of locks and processes that cause
79 processes to inherit priorities from a previous process that is
107 waiters - A list of processes that are blocked on a mutex.
115 differentiate between two processes that are being described together.
121 The PI chain is a list of processes and mutexes that may cause priority
162 For PI to work, the processes at the right end of these chains (or we may
164 than the processes to the left or below in the chain.
264 Now we add 4 processes that run each of these functions separately.
[all …]
|
