Searched refs:cgroups (Results 1 – 25 of 35) sorted by relevance
12
| /Linux-v4.19/Documentation/cgroup-v1/ |
| D | 00-INDEX | 5 cgroups.txt
22 - Network classifier cgroups details and usages.
24 - Network priority cgroups details and usages.
26 - Process number cgroups details and usages.
|
| D | cgroups.txt | 17 1.1 What are cgroups ?
18 1.2 Why are cgroups needed ?
19 1.3 How are cgroups implemented ?
22 1.6 How do I use cgroups ?
37 1.1 What are cgroups ?
50 facilities provided by cgroups to treat groups of tasks in
56 A *hierarchy* is a set of cgroups arranged in a tree, such that
57 every task in the system is in exactly one of the cgroups in the
63 cgroups. Each hierarchy is a partition of all tasks in the system.
65 User-level code may create and destroy cgroups by name in an
[all …]
|
| D | net_cls.txt | 8 different priorities to packets from different cgroups.
12 Creating a net_cls cgroups instance creates a net_cls.classid file.
|
| D | devices.txt | 38 Any task can move itself between cgroups. This clearly won't
54 device cgroups maintain hierarchy by making sure a cgroup never has more
106 not be possible once the device cgroups has children.
110 device cgroups is implemented internally using a behavior (ALLOW, DENY) and a
|
| D | freezer-subsystem.txt | 5 whole. The cgroup freezer uses cgroups to describe the set of tasks to
53 tasks belonging to the cgroup and all its descendant cgroups. Each
69 to the cgroup or one of its descendant cgroups until the new task is
75 descendant cgroups.
|
| D | blkio-controller.txt | 23 cgroups. Here is what you can do.
32 cgroups.txt, Why are cgroups needed?.
38 - Create two cgroups
64 ideally io.disk_time of cgroups should be in proportion to the weight.
74 - Mount blkio controller (see cgroups.txt, Why are cgroups needed?)
180 competing with the cgroup's child cgroups. For details,
278 from other queues/cgroups. This is in nanoseconds. If this is read
293 include stats from all the descendant cgroups.
|
| D | memory.txt | 250 The reclaim algorithm has not been modified for cgroups, except that
283 Kernel memory accounting is enabled for all memory cgroups by default. But
354 3.1. Prepare the cgroups (see cgroups.txt, Why are cgroups needed?)
528 (Note: file and shmem may be shared among other cgroups. In that case,
586 The hierarchy is created by creating the appropriate cgroups in the
616 cgroups created below it, or if the parent cgroup has use_hierarchy
653 reclaiming memory for balancing between memory cgroups
714 Memory cgroup implements memory thresholds using the cgroups notification
715 API (see cgroups.txt). It allows to register multiple memory and memsw
734 API (See cgroups.txt). It allows to register multiple OOM notification
[all …]
|
| D | cpuacct.txt | 4 The CPU accounting controller is used to group tasks using cgroups and
|
| D | net_prio.txt | 38 echo "eth0 5" > /sys/fs/cgroups/net_prio/iscsi/net_prio.ifpriomap
|
| D | pids.txt | 30 all new cgroups (N.B. that PID limits are hierarchical, so the most stringent
|
| D | rdma.txt | 55 rdma resources. Linking resources around css also ensures that cgroups can be
|
| D | memcg_test.txt | 263 Memory controller implements memory thresholds using cgroups notification
|
| /Linux-v4.19/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 93 multiple individual control groups, the plural form "cgroups" is used.
110 cgroups form a tree structure and every process in the system belongs
120 processes which belong to the cgroups consisting the inclusive
190 A given cgroup may have multiple child cgroups forming a tree
256 different cgroups and are not subject to the no internal process
257 constraint - threaded controllers can be enabled on non-leaf cgroups
263 can't have populated child cgroups which aren't threaded. Because the
265 serve both as a threaded domain and a parent to domain cgroups.
329 between threads in a non-leaf cgroup and its child cgroups. Each
353 both cgroups.
[all …]
|
| /Linux-v4.19/block/ |
| D | Kconfig.iosched | 101 (cgroups-v1) or io (cgroups-v2) controller.
|
| D | Kconfig | 115 cgroups and specifying per device IO rate policies.
125 effort limit to prioritize cgroups. Depending on the setting, the limit
126 can be used to protect cgroups in terms of bandwidth/iops and better
|
| /Linux-v4.19/Documentation/accounting/ |
| D | cgroupstats.txt | 7 and attributes specific to cgroups. It should be very easy to
|
| /Linux-v4.19/Documentation/block/ |
| D | bfq-iosched.txt | 5 low-latency capabilities. In addition to cgroups support (blkio or io
297 Unless the cgroups interface is used (see "4. BFQ group scheduling"),
477 BFQ supports both cgroups-v1 and cgroups-v2 io controllers, namely
479 share. To activate cgroups support, set BFQ_GROUP_IOSCHED.
513 prefix. So, with cgroups-v1 or cgroups-v2, the full prefix for
518 As for cgroups-v1 (blkio controller), the exact set of stat files
|
| D | queue-sysfs.txt | 124 per-block-cgroup request pool. IOW, if there are N block cgroups,
193 blk-throttle makes decision based on the samplings. Lower time means cgroups
|
| D | cfq-iosched.txt | 160 composed of five cgroups - root, A, B, AA and AB - with the following
185 If all cgroups have active IOs and competing with each other, disk
|
| /Linux-v4.19/include/linux/ |
| D | cgroup.h | 435 rcu_dereference_check((task)->cgroups, \
441 rcu_dereference((task)->cgroups)
|
| /Linux-v4.19/tools/perf/Documentation/ |
| D | perf-trace.txt | 70 Look for cgroups to set at the /sys/fs/cgroup/perf_event directory, then
84 Multiple cgroups:
|
| /Linux-v4.19/tools/bpf/bpftool/Documentation/ |
| D | bpftool-cgroup.rst | 44 Iterate over all cgroups in *CGROUP_ROOT* and list all
|
| /Linux-v4.19/Documentation/scheduler/ |
| D | sched-design-CFS.txt | 218 Documentation/cgroup-v1/cgroups.txt for more information about this filesystem.
222 task groups and modify their CPU share using the "cgroups" pseudo filesystem.
|
| D | sched-rt-group.txt | 136 Documentation/cgroup-v1/cgroups.txt as well.
|
| /Linux-v4.19/Documentation/ |
| D | kernel-per-CPU-kthreads.txt | 15 - Documentation/cgroup-v1: Using cgroups to bind tasks to sets of CPUs.
331 1. Use affinity, cgroups, or other mechanism to force these kthreads
|
12
