Searched refs:ancestors (Results 1 – 14 of 14) sorted by relevance
| /linux-5.19.10/block/ |
| D | blk-iocost.c | 546 struct ioc_gq *ancestors[]; member
1091 struct ioc_gq *parent = iocg->ancestors[lvl]; in __propagate_weights()
1092 struct ioc_gq *child = iocg->ancestors[lvl + 1]; in __propagate_weights()
1171 struct ioc_gq *parent = iocg->ancestors[lvl]; in current_hweight()
1172 struct ioc_gq *child = iocg->ancestors[lvl + 1]; in current_hweight()
1213 struct ioc_gq *parent = iocg->ancestors[lvl]; in current_hweight_max()
1214 struct ioc_gq *child = iocg->ancestors[lvl + 1]; in current_hweight_max()
1276 if (!list_empty(&iocg->ancestors[i]->active_list)) in iocg_activate()
1630 if (!list_empty(&iocg->ancestors[lvl]->walk_list)) in iocg_build_inner_walk()
1636 struct ioc_gq *inner = iocg->ancestors[lvl]; in iocg_build_inner_walk()
[all …]
|
| /linux-5.19.10/Documentation/filesystems/nfs/ |
| D | exporting.rst | 36 all of the ancestors of that filesystem object are also in the dcache.
67 Note that such a dentry can acquire children, name, ancestors, etc.
199 filesystem is exported however, then nfsd must walk the ancestors of the
|
| /linux-5.19.10/Documentation/admin-guide/cgroup-v1/ |
| D | freezer-subsystem.rst | 94 Shows the parent-state. 0 if none of the cgroup's ancestors is
|
| D | memory.rst | 667 usage of e, is accounted to its ancestors up until the root (i.e, c and root).
668 If one of the ancestors goes over its limit, the reclaim algorithm reclaims
|
| D | cpusets.rst | 137 cpuset (except direct ancestors and descendants) may contain
|
| /linux-5.19.10/Documentation/filesystems/ |
| D | directory-locking.rst | 47 * lock parents in "ancestors first" order.
|
| D | sysfs.rst | 43 ancestors of object hierarchies; i.e. the subsystems the objects
|
| /linux-5.19.10/Documentation/core-api/ |
| D | rbtree.rst | 264 node and its ancestors, up to a given stop point (or NULL to update
|
| /linux-5.19.10/Documentation/driver-api/ |
| D | device_link.rst | 224 all its ancestors. That is achieved by traversing the ACPI namespace
|
| /linux-5.19.10/Documentation/firmware-guide/acpi/ |
| D | enumeration.rst | 524 ancestors provides a _DSD with a valid "compatible" property. Such device
|
| /linux-5.19.10/Documentation/admin-guide/mm/ |
| D | hugetlbpage.rst | 338 ancestors, such as numactl. This means that if the task is invoked from a
|
| /linux-5.19.10/Documentation/driver-api/pm/ |
| D | devices.rst | 362 of its ancestors. The second flag, when set, informs the middle layer
|
| /linux-5.19.10/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 635 as long as the usages of all its ancestors are under their
2200 Sometimes, external factors like changes to ancestors'
|
| /linux-5.19.10/Documentation/power/ |
| D | pci.rst | 1010 affects all of the ancestors of the device, so this flag should only be used if
|