| /kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
| D | dvb_intro.rst | 153 HIERARCHY = NONE
181 HIERARCHY = NONE
196 HIERARCHY = NONE
211 HIERARCHY = NONE
226 HIERARCHY = NONE
241 HIERARCHY = NONE
256 HIERARCHY = NONE
271 HIERARCHY = NONE
286 HIERARCHY = NONE
301 HIERARCHY = NONE
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/cgroup-v1/ |
| D | cgroups.rst | 60 A *hierarchy* is a set of cgroups arranged in a tree, such that
62 hierarchy, and a set of subsystems; each subsystem has system-specific
63 state attached to each cgroup in the hierarchy. Each hierarchy has
67 cgroups. Each hierarchy is a partition of all tasks in the system.
72 a cgroup. Those creations and assignments only affect the hierarchy
99 Multiple hierarchy support is provided to allow for situations where
102 hierarchy to be a natural division of tasks, without having to handle
108 separate hierarchy; at the other extreme, all subsystems
109 would be attached to the same hierarchy.
147 With only a single hierarchy, he now would potentially have to create
[all …]
|
| D | pids.rst | 8 The process number controller is used to allow a cgroup hierarchy to stop any
13 preventable in the scope of a cgroup hierarchy by allowing resource limiting of
32 limit in the hierarchy is followed).
49 Then we create a hierarchy, set limits and attach processes to it::
68 not be able to overcome the most stringent limit in the hierarchy (in this case,
|
| /kernel/linux/linux-4.19/Documentation/cgroup-v1/ |
| D | cgroups.txt | 56 A *hierarchy* is a set of cgroups arranged in a tree, such that
58 hierarchy, and a set of subsystems; each subsystem has system-specific
59 state attached to each cgroup in the hierarchy. Each hierarchy has
63 cgroups. Each hierarchy is a partition of all tasks in the system.
68 a cgroup. Those creations and assignments only affect the hierarchy
95 Multiple hierarchy support is provided to allow for situations where
98 hierarchy to be a natural division of tasks, without having to handle
104 separate hierarchy; at the other extreme, all subsystems
105 would be attached to the same hierarchy.
143 With only a single hierarchy, he now would potentially have to create
[all …]
|
| D | pids.txt | 7 The process number controller is used to allow a cgroup hierarchy to stop any
12 preventable in the scope of a cgroup hierarchy by allowing resource limiting of
31 limit in the hierarchy is followed).
43 Then we create a hierarchy, set limits and attach processes to it:
61 not be able to overcome the most stringent limit in the hierarchy (in this case,
|
| D | devices.txt | 52 4. Hierarchy
54 device cgroups maintain hierarchy by making sure a cgroup never has more
108 4.1 Hierarchy (internal implementation)
114 to devices will be propagated down the hierarchy.
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | IRQ-domain.txt | 188 Hierarchy IRQ domain
205 interrupt controller and those irq_domains are organized into hierarchy.
206 When building irq_domain hierarchy, the irq_domain near to the device is
207 child and the irq_domain near to CPU is parent. So a hierarchy structure
218 There are four major interfaces to use hierarchy irq_domain:
229 Following changes are needed to support hierarchy irq_domain:
232 maintain irq_domain hierarchy information.
234 build hierarchy irq_data to match hierarchy irq_domains. The irq_data
236 3) new callbacks are added to struct irq_domain_ops to support hierarchy
239 With support of hierarchy irq_domain and hierarchy irq_data ready, an
[all …]
|
| /kernel/linux/linux-5.10/Documentation/core-api/irq/ |
| D | irq-domain.rst | 188 Hierarchy IRQ domain
205 interrupt controller and those irq_domains are organized into hierarchy.
206 When building irq_domain hierarchy, the irq_domain near to the device is
207 child and the irq_domain near to CPU is parent. So a hierarchy structure
218 There are four major interfaces to use hierarchy irq_domain:
229 Following changes are needed to support hierarchy irq_domain:
232 maintain irq_domain hierarchy information.
234 build hierarchy irq_data to match hierarchy irq_domains. The irq_data
236 3) new callbacks are added to struct irq_domain_ops to support hierarchy
239 With support of hierarchy irq_domain and hierarchy irq_data ready, an
[all …]
|
| /kernel/linux/linux-4.19/drivers/media/dvb-frontends/ |
| D | as102_fe.c | 134 switch (c->hierarchy) { in as102_fe_set_frontend()
136 tune_args.hierarchy = HIER_NONE; in as102_fe_set_frontend()
139 tune_args.hierarchy = HIER_ALPHA_1; in as102_fe_set_frontend()
142 tune_args.hierarchy = HIER_ALPHA_2; in as102_fe_set_frontend()
145 tune_args.hierarchy = HIER_ALPHA_4; in as102_fe_set_frontend()
148 tune_args.hierarchy = HIER_UNKNOWN; in as102_fe_set_frontend()
158 * Detect a hierarchy selection in as102_fe_set_frontend()
161 if ((tune_args.hierarchy != HIER_NONE) && in as102_fe_set_frontend()
178 tune_args.hierarchy, in as102_fe_set_frontend()
218 /* extract hierarchy */ in as102_fe_get_frontend()
[all …]
|
| D | as102_fe_types.h | 28 /* hierarchy priority selection values */
39 /* hierarchy available values */
110 uint8_t hierarchy; member
126 /* hierarchy selection */
130 /* hierarchy */
131 uint8_t hierarchy; member
|
| D | dib3000mb.c | 228 switch (c->hierarchy) { in dib3000mb_set_frontend()
230 deb_setf("hierarchy: none\n"); in dib3000mb_set_frontend()
233 deb_setf("hierarchy: alpha=1\n"); in dib3000mb_set_frontend()
237 deb_setf("hierarchy: alpha=2\n"); in dib3000mb_set_frontend()
241 deb_setf("hierarchy: alpha=4\n"); in dib3000mb_set_frontend()
245 deb_setf("hierarchy: alpha=auto\n"); in dib3000mb_set_frontend()
251 if (c->hierarchy == HIERARCHY_NONE) { in dib3000mb_set_frontend()
255 } else if (c->hierarchy != HIERARCHY_AUTO) { in dib3000mb_set_frontend()
332 c->hierarchy == HIERARCHY_AUTO || in dib3000mb_set_frontend()
508 c->hierarchy = HIERARCHY_NONE; in dib3000mb_get_frontend()
[all …]
|
| /kernel/linux/linux-5.10/drivers/media/dvb-frontends/ |
| D | as102_fe.c | 125 switch (c->hierarchy) { in as102_fe_set_frontend()
127 tune_args.hierarchy = HIER_NONE; in as102_fe_set_frontend()
130 tune_args.hierarchy = HIER_ALPHA_1; in as102_fe_set_frontend()
133 tune_args.hierarchy = HIER_ALPHA_2; in as102_fe_set_frontend()
136 tune_args.hierarchy = HIER_ALPHA_4; in as102_fe_set_frontend()
139 tune_args.hierarchy = HIER_UNKNOWN; in as102_fe_set_frontend()
149 * Detect a hierarchy selection in as102_fe_set_frontend()
152 if ((tune_args.hierarchy != HIER_NONE) && in as102_fe_set_frontend()
169 tune_args.hierarchy, in as102_fe_set_frontend()
209 /* extract hierarchy */ in as102_fe_get_frontend()
[all …]
|
| D | as102_fe_types.h | 19 /* hierarchy priority selection values */
30 /* hierarchy available values */
101 uint8_t hierarchy; member
117 /* hierarchy selection */
121 /* hierarchy */
122 uint8_t hierarchy; member
|
| D | dib3000mb.c | 224 switch (c->hierarchy) { in dib3000mb_set_frontend()
226 deb_setf("hierarchy: none\n"); in dib3000mb_set_frontend()
229 deb_setf("hierarchy: alpha=1\n"); in dib3000mb_set_frontend()
233 deb_setf("hierarchy: alpha=2\n"); in dib3000mb_set_frontend()
237 deb_setf("hierarchy: alpha=4\n"); in dib3000mb_set_frontend()
241 deb_setf("hierarchy: alpha=auto\n"); in dib3000mb_set_frontend()
247 if (c->hierarchy == HIERARCHY_NONE) { in dib3000mb_set_frontend()
251 } else if (c->hierarchy != HIERARCHY_AUTO) { in dib3000mb_set_frontend()
328 c->hierarchy == HIERARCHY_AUTO || in dib3000mb_set_frontend()
504 c->hierarchy = HIERARCHY_NONE; in dib3000mb_get_frontend()
[all …]
|
| D | stv0367_priv.h | 103 FE_TER_HIER_NONE, /*Hierarchy None*/
104 FE_TER_HIER_LOW_PRIO, /*Hierarchy : Low Priority*/
105 FE_TER_HIER_HIGH_PRIO, /*Hierarchy : High Priority*/
106 FE_TER_HIER_PRIO_ANY /*Hierarchy :Any*/
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | cgroup-defs.h | 96 __CFTYPE_ONLY_ON_DFL = (1 << 16), /* only on default hierarchy */
97 __CFTYPE_NOT_ON_DFL = (1 << 17), /* not on default hierarchy */
272 * hierarchy on reads.
325 * idr allocated in-hierarchy ID.
336 * step down the hierarchy increments the level. This along with
338 * descendant of another without traversing the hierarchy.
405 * On the default hierarchy, a css_set for a cgroup with some
456 * A cgroup_root represents the root of a cgroup hierarchy, and may be
457 * associated with a kernfs_root to form an active hierarchy. This is
463 /* The bitmask of subsystems attached to this hierarchy */
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | cgroup-defs.h | 115 __CFTYPE_ONLY_ON_DFL = (1 << 16), /* only on default hierarchy */
116 __CFTYPE_NOT_ON_DFL = (1 << 17), /* not on default hierarchy */
291 * hierarchy on reads.
364 * step down the hierarchy increments the level. This along with
366 * descendant of another without traversing the hierarchy.
433 * On the default hierarchy, a css_set for a cgroup with some
490 * A cgroup_root represents the root of a cgroup hierarchy, and may be
491 * associated with a kernfs_root to form an active hierarchy. This is
497 /* The bitmask of subsystems attached to this hierarchy */
500 /* Unique id for this hierarchy. */
[all …]
|
| /kernel/linux/linux-4.19/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 100 distribute system resources along the hierarchy in a controlled and
106 distributing a specific type of system resource along the hierarchy
121 sub-hierarchy of the cgroup. When a controller is enabled on a nested
123 restrictions set closer to the root in the hierarchy can not be
133 Unlike v1, cgroup v2 has only single hierarchy. The cgroup v2
134 hierarchy can be mounted with the following mount command::
139 controllers which support v2 and are not bound to a v1 hierarchy are
140 automatically bound to the v2 hierarchy and show up at the root.
141 Controllers which are not in active use in the v2 hierarchy can be
142 bound to other hierarchies. This allows mixing v2 hierarchy with the
[all …]
|
| /kernel/linux/linux-5.10/fs/9p/ |
| D | v9fs.h | 17 * @V9FS_ACCESS_SINGLE: only the mounting user can access the hierarchy
67 * @uname: string user name to mount hierarchy as
68 * @aname: mount specifier for remote hierarchy
70 * @dfltuid: default numeric userid to mount hierarchy as
71 * @dfltgid: default numeric groupid to mount hierarchy as
72 * @uid: if %V9FS_ACCESS_SINGLE, the numeric uid which mounted the hierarchy
96 char *aname; /* name of remote hierarchy being mounted */
|
| /kernel/linux/linux-4.19/fs/9p/ |
| D | v9fs.h | 32 * @V9FS_ACCESS_SINGLE: only the mounting user can access the hierarchy
82 * @uname: string user name to mount hierarchy as
83 * @aname: mount specifier for remote hierarchy
85 * @dfltuid: default numeric userid to mount hierarchy as
86 * @dfltgid: default numeric groupid to mount hierarchy as
87 * @uid: if %V9FS_ACCESS_SINGLE, the numeric uid which mounted the hierarchy
111 char *aname; /* name of remote hierarchy being mounted */
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 104 distribute system resources along the hierarchy in a controlled and
110 distributing a specific type of system resource along the hierarchy
125 sub-hierarchy of the cgroup. When a controller is enabled on a nested
127 restrictions set closer to the root in the hierarchy can not be
137 Unlike v1, cgroup v2 has only single hierarchy. The cgroup v2
138 hierarchy can be mounted with the following mount command::
143 controllers which support v2 and are not bound to a v1 hierarchy are
144 automatically bound to the v2 hierarchy and show up at the root.
145 Controllers which are not in active use in the v2 hierarchy can be
146 bound to other hierarchies. This allows mixing v2 hierarchy with the
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/opp/ |
| D | opp.txt | 147 It's a user defined array containing a hierarchy of hardware version numbers,
148 supported by the OPP. For example: a platform with hierarchy of three levels
150 corresponds to Version hierarchy A, Y corresponds to version hierarchy B and Z
151 corresponds to version hierarchy C.
153 Each level of hierarchy is represented by a 32 bit value, and so there can be
154 only 32 different supported version per hierarchy. i.e. 1 bit per version. A
155 value of 0xFFFFFFFF will enable the OPP for all versions for that hierarchy
159 If 32 values aren't sufficient for a version hierarchy, than that version
160 hierarchy can be contained in multiple 32 bit values. i.e. <X Y Z1 Z2> in the
161 above example, Z1 & Z2 refer to the version hierarchy Z.
[all …]
|
| /kernel/linux/linux-5.10/drivers/edac/ |
| D | debugfs.c | 82 /* Create a toplevel dir under EDAC's debugfs hierarchy */
92 /* Create a toplevel dir under EDAC's debugfs hierarchy with parent @parent */
101 * Create a file under EDAC's hierarchy or a sub-hierarchy:
|
| /kernel/linux/linux-4.19/drivers/usb/gadget/function/ |
| D | uvc_configfs.c | 75 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ \
99 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ \
213 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ \
251 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ in uvcg_default_processing_bm_controls_show()
319 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ \
365 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ in uvcg_default_camera_bm_controls_show()
436 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ \
531 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ in uvcg_control_class_allow_link()
572 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ in uvcg_control_class_drop_link()
667 mutex_lock(su_mutex); /* for navigating configfs hierarchy */ in uvcg_format_bma_controls_show()
[all …]
|
| /kernel/linux/linux-4.19/drivers/edac/ |
| D | debugfs.c | 105 /* Create a toplevel dir under EDAC's debugfs hierarchy */
115 /* Create a toplevel dir under EDAC's debugfs hierarchy with parent @parent */
124 * Create a file under EDAC's hierarchy or a sub-hierarchy:
|