/linux-6.1.9/tools/testing/selftests/bpf/prog_tests/ |
D | cgroup_hierarchical_stats.c | 54 } cgroups[] = { variable 64 #define N_CGROUPS ARRAY_SIZE(cgroups) 133 fd = create_and_get_cgroup(cgroups[i].path); in setup_cgroups() 137 cgroups[i].fd = fd; in setup_cgroups() 138 cgroups[i].id = get_cgroup_id(cgroups[i].path); in setup_cgroups() 147 close(cgroups[i].fd); in cleanup_cgroups() 175 if (join_parent_cgroup(cgroups[i].path)) in attach_processes() 220 attach_counters[i] = get_attach_counter(cgroups[i].id, in check_attach_counters() 221 cgroups[i].name); in check_attach_counters() 288 err = setup_cgroup_iter(*skel, cgroups[i].fd, cgroups[i].name); in setup_progs() [all …]
|
/linux-6.1.9/tools/cgroup/ |
D | memcg_shrinker.py | 12 cgroups = {} 18 cgroups[ino] = path 21 return cgroups 45 cgroups = scan_cgroups("/sys/fs/cgroup/") 59 cg = cgroups[ino]
|
/linux-6.1.9/tools/perf/util/ |
D | cgroup.c | 560 down_write(&env->cgroups.lock); in cgroup__findnew() 561 cgrp = __cgroup__findnew(&env->cgroups.tree, id, true, path); in cgroup__findnew() 562 up_write(&env->cgroups.lock); in cgroup__findnew() 570 down_read(&env->cgroups.lock); in cgroup__find() 571 cgrp = __cgroup__findnew(&env->cgroups.tree, id, false, NULL); in cgroup__find() 572 up_read(&env->cgroups.lock); in cgroup__find() 581 down_write(&env->cgroups.lock); in perf_env__purge_cgroups() 582 while (!RB_EMPTY_ROOT(&env->cgroups.tree)) { in perf_env__purge_cgroups() 583 node = rb_first(&env->cgroups.tree); in perf_env__purge_cgroups() 586 rb_erase(node, &env->cgroups.tree); in perf_env__purge_cgroups() [all …]
|
D | cgroup.h | 30 int evlist__expand_cgroup(struct evlist *evlist, const char *cgroups,
|
D | env.h | 115 } cgroups; member
|
/linux-6.1.9/Documentation/admin-guide/cgroup-v1/ |
D | cgroups.rst | 21 1.1 What are cgroups ? 22 1.2 Why are cgroups needed ? 23 1.3 How are cgroups implemented ? 26 1.6 How do I use cgroups ? 41 1.1 What are cgroups ? 54 facilities provided by cgroups to treat groups of tasks in 60 A *hierarchy* is a set of cgroups arranged in a tree, such that 61 every task in the system is in exactly one of the cgroups in the 67 cgroups. Each hierarchy is a partition of all tasks in the system. 69 User-level code may create and destroy cgroups by name in an [all …]
|
D | net_cls.rst | 9 different priorities to packets from different cgroups. 13 Creating a net_cls cgroups instance creates a net_cls.classid file.
|
D | devices.rst | 43 Any task can move itself between cgroups. This clearly won't 60 device cgroups maintain hierarchy by making sure a cgroup never has more 121 not be possible once the device cgroups has children. 126 device cgroups is implemented internally using a behavior (ALLOW, DENY) and a
|
D | index.rst | 10 cgroups
|
D | freezer-subsystem.rst | 9 whole. The cgroup freezer uses cgroups to describe the set of tasks to 57 tasks belonging to the cgroup and all its descendant cgroups. Each 73 to the cgroup or one of its descendant cgroups until the new task is 79 descendant cgroups.
|
D | memory.rst | 273 The reclaim algorithm has not been modified for cgroups, except that 310 Kernel memory accounting is enabled for all memory cgroups by default. But 390 3.1. Prepare the cgroups (see cgroups.txt, Why are cgroups needed?) 588 (Note: file and shmem may be shared among other cgroups. In that case, 652 The hierarchy is created by creating the appropriate cgroups in the 714 reclaiming memory for balancing between memory cgroups 787 Memory cgroup implements memory thresholds using the cgroups notification 788 API (see cgroups.txt). It allows to register multiple memory and memsw 809 API (See cgroups.txt). It allows to register multiple OOM notification 878 events are not pass-through. For example, you have three cgroups: A->B->C. Now [all …]
|
D | memcg_test.rst | 213 9.5 nested cgroups 216 Use tests like the following for testing nested cgroups:: 325 Memory controller implements memory thresholds using cgroups notification
|
D | blkio-controller.rst | 31 Mount blkio controller (see cgroups.txt, Why are cgroups needed?):: 233 from other queues/cgroups. This is in nanoseconds. If this is read 248 include stats from all the descendant cgroups.
|
/linux-6.1.9/Documentation/admin-guide/ |
D | cgroup-v2.rst | 103 multiple individual control groups, the plural form "cgroups" is used. 120 cgroups form a tree structure and every process in the system belongs 130 processes which belong to the cgroups consisting the inclusive 206 propagation into leaf cgroups. This allows protecting entire 225 A given cgroup may have multiple child cgroups forming a tree 291 different cgroups and are not subject to the no internal process 292 constraint - threaded controllers can be enabled on non-leaf cgroups 298 can't have populated child cgroups which aren't threaded. Because the 300 serve both as a threaded domain and a parent to domain cgroups. 364 between threads in a non-leaf cgroup and its child cgroups. Each [all …]
|
/linux-6.1.9/block/ |
D | Kconfig.iosched | 37 (cgroups-v1) or io (cgroups-v2) controller.
|
D | Kconfig | 96 cgroups and specifying per device IO rate policies. 105 effort limit to prioritize cgroups. Depending on the setting, the limit 106 can be used to protect cgroups in terms of bandwidth/iops and better
|
/linux-6.1.9/tools/perf/util/bpf_skel/ |
D | off_cpu.bpf.c | 125 return BPF_CORE_READ(t, cgroups, dfl_cgrp, kn, id); in get_cgroup_id() 136 cgrp = BPF_CORE_READ(t, cgroups, subsys[perf_subsys_id], cgroup); in get_cgroup_id()
|
D | bperf_cgroup.bpf.c | 97 cgrp = BPF_CORE_READ(p, cgroups, subsys[perf_subsys_id], cgroup); in get_cgroup_v1_idx()
|
/linux-6.1.9/include/linux/ |
D | psi.h | 62 rcu_assign_pointer(p->cgroups, to); in cgroup_move_task()
|
/linux-6.1.9/Documentation/bpf/ |
D | map_cgroup_storage.rst | 10 attach to cgroups; the programs are made available by the same Kconfig. The 16 cgroups on their own. 132 that uses the map. A program may be attached to multiple cgroups or have
|
/linux-6.1.9/Documentation/accounting/ |
D | cgroupstats.rst | 11 and attributes specific to cgroups. It should be very easy to
|
/linux-6.1.9/Documentation/translations/zh_CN/accounting/ |
D | psi.rst | 151 对于CONFIG_CGROUP=y及挂载了cgroup2文件系统的系统,能够获取cgroups内任务的psi。
|
/linux-6.1.9/Documentation/translations/zh_CN/scheduler/ |
D | sched-design-CFS.rst | 183 关于该文件系统的更多信息,参见Documentation/admin-guide/cgroup-v1/cgroups.rst
|
/linux-6.1.9/tools/testing/selftests/vm/ |
D | charge_reserved_hugetlb.sh | 504 echo Test normal case, multiple cgroups. 550 echo Test normal case with write, multiple cgroups.
|
/linux-6.1.9/Documentation/block/ |
D | bfq-iosched.rst | 6 low-latency capabilities. In addition to cgroups support (blkio or io 318 Unless the cgroups interface is used (see "4. BFQ group scheduling"), 498 BFQ supports both cgroups-v1 and cgroups-v2 io controllers, namely 500 share. To activate cgroups support, set BFQ_GROUP_IOSCHED. 534 prefix. So, with cgroups-v1 or cgroups-v2, the full prefix for 539 As for cgroups-v1 (blkio controller), the exact set of stat files
|