Searched refs:ancestors (Results 1 – 14 of 14) sorted by relevance
/Linux-v5.4/block/ |
D | blk-iocost.c | 500 struct ioc_gq *ancestors[]; member 904 struct ioc_gq *parent = iocg->ancestors[lvl]; in __propagate_active_weight() 905 struct ioc_gq *child = iocg->ancestors[lvl + 1]; in __propagate_active_weight() 983 struct ioc_gq *parent = iocg->ancestors[lvl]; in current_hweight() 984 struct ioc_gq *child = iocg->ancestors[lvl + 1]; in current_hweight() 1063 if (!list_empty(&iocg->ancestors[i]->active_list)) in iocg_activate() 1979 iocg = kzalloc_node(sizeof(*iocg) + levels * sizeof(iocg->ancestors[0]), in ioc_pd_alloc() 2017 iocg->ancestors[tiocg->level] = tiocg; in ioc_pd_init()
|
/Linux-v5.4/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.
|
/Linux-v5.4/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 | 683 usage of e, is accounted to its ancestors up until the root (i.e, c and root), 684 that has memory.use_hierarchy enabled. If one of the ancestors goes over its
|
D | cpusets.rst | 135 cpuset (except direct ancestors and descendants) may contain
|
/Linux-v5.4/Documentation/filesystems/ |
D | directory-locking.rst | 47 * lock parents in "ancestors first" order.
|
D | sysfs.txt | 39 ancestors of object hierarchies; i.e. the subsystems the objects
|
/Linux-v5.4/Documentation/ |
D | rbtree.txt | 264 node and its ancestors, up to a given stop point (or NULL to update
|
/Linux-v5.4/Documentation/firmware-guide/acpi/ |
D | enumeration.rst | 452 ancestors provides a _DSD with a valid "compatible" property. Such device
|
/Linux-v5.4/Documentation/driver-api/ |
D | device_link.rst | 228 all its ancestors. That is achieved by traversing the ACPI namespace
|
/Linux-v5.4/Documentation/admin-guide/mm/ |
D | hugetlbpage.rst | 245 ancestors, such as numactl. This means that if the task is invoked from a
|
/Linux-v5.4/Documentation/driver-api/pm/ |
D | devices.rst | 370 of its ancestors. The second flag, when set, informs the middle layer
|
/Linux-v5.4/Documentation/admin-guide/ |
D | cgroup-v2.rst | 619 as long as the usages of all its ancestors are under their 1960 Sometimes, external factors like changes to ancestors'
|
/Linux-v5.4/Documentation/power/ |
D | pci.rst | 1010 the ancestors of the device, so this flag should only be used if absolutely
|