Home
last modified time | relevance | path

Searched refs:hierarchy (Results 1 – 25 of 68) sorted by relevance

123

/f-stack/dpdk/doc/guides/prog_guide/
H A Dtraffic_management.rst19 * Capability query API per port, per hierarchy level and per hierarchy node
23 * Congestion management for hierarchy leaf nodes: algorithms of tail drop, head
63 at the level of each node of the scheduling hierarchy, regardless of the node
78 limiters) for the hierarchy nodes, subject to the specific implementation
81 Each hierarchy node has zero or one private shaper (only one node using it)
107 hierarchy, subject to the specific implementation supporting them.
179 The hierarchy is specified by incrementally adding nodes to build up the
190 its sibling nodes. At this time, since the hierarchy is not fully defined,
201 * It validates the start-up hierarchy that was previously defined for the
209 hierarchy configuration (e.g. a hierarchy with less leaf nodes), which can be
[all …]
/f-stack/freebsd/contrib/openzfs/tests/zfs-tests/tests/functional/inheritance/
H A Dstate012.cfg33 # Verify that running 'zfs inherit -r' at each level of the data hierarchy
36 # hierarchy.
40 # should propagate down the entire data hierarchy. Done for completeness
H A Dstate014.cfg33 # Verify that running 'zfs inherit -r' at each level of the data hierarchy
36 # hierarchy.
40 # should propagate down the entire data hierarchy. Done for completeness
H A Dstate024.cfg33 # Verify that executing 'zfs inherit -r' at the top level in the hierarchy
36 # values being propagated down the hierarchy.
H A Dstate018.cfg33 # Verify that executing 'zfs inherit -r' at the top level in the hierarchy
38 # hierarchy.
H A DREADME.config26 # The configX.cfg files describe both the dataset hierarchy to
50 # dataset hierarchy.
H A Dstate003.cfg35 # the properties of datasets above it in the hierarchy.
H A DREADME.state29 # dataset hierarchy which has been specified by the corresponding
61 # the data hierarchy.
H A Dstate007.cfg35 # hierarchy independently.
H A Dstate009.cfg34 # data hierarchy where the properties of each dataset have their
/f-stack/freebsd/contrib/device-tree/Bindings/opp/
H A Dopp.txt161 It's a user defined array containing a hierarchy of hardware version numbers,
162 supported by the OPP. For example: a platform with hierarchy of three levels
164 corresponds to Version hierarchy A, Y corresponds to version hierarchy B and Z
165 corresponds to version hierarchy C.
167 Each level of hierarchy is represented by a 32 bit value, and so there can be
168 only 32 different supported version per hierarchy. i.e. 1 bit per version. A
169 value of 0xFFFFFFFF will enable the OPP for all versions for that hierarchy
173 If 32 values aren't sufficient for a version hierarchy, than that version
174 hierarchy can be contained in multiple 32 bit values. i.e. <X Y Z1 Z2> in the
175 above example, Z1 & Z2 refer to the version hierarchy Z.
[all …]
/f-stack/freebsd/contrib/device-tree/Bindings/arm/omap/
H A Dprcm.txt4 a DT hierarchy. Each TI SoC can have multiple PRCM entities listed for it,
5 each describing one module and the clock hierarchy under it. see [1] for
H A Dprm-inst.txt6 hierarchy.
/f-stack/freebsd/contrib/device-tree/Bindings/cpu/
H A Dcpu-topology.txt9 In a SMP system, the hierarchy of CPUs is defined through three entities that
17 The bottom hierarchy level sits at core or thread level depending on whether
21 threads existing in the system and map to the hierarchy level "thread" above.
23 in the system and map to the hierarchy level "core" above.
26 corresponding to the system hierarchy; syntactically they are defined as device
33 correspond to physical CPUs and are to be mapped to the hierarchy levels.
92 levels) since name uniqueness will be guaranteed by the device tree hierarchy.
/f-stack/freebsd/contrib/device-tree/src/arm/
H A Dspear1310-evb.dts355 pl022,hierarchy = <0>;
388 pl022,hierarchy = <0>;
404 pl022,hierarchy = <0>;
H A Dspear1340-evb.dts448 pl022,hierarchy = <0>;
464 pl022,hierarchy = <0>;
498 pl022,hierarchy = <0>;
/f-stack/freebsd/contrib/device-tree/Bindings/power/
H A Drenesas,sysc-rmobile.txt23 - pm-domains: This node contains a hierarchy of PM domain nodes, which should
52 This shows a subset of the r8a7740 PM domain hierarchy, containing the
/f-stack/freebsd/contrib/device-tree/Bindings/arm/msm/
H A Dqcom,idle-state.txt18 hierarchy to enter standby states, when all cpus are idle. An interrupt brings
20 cache hierarchy is also out of standby, and then the cpu is allowed to resume
39 system state including cache hierarchy is ready before allowing core to
/f-stack/freebsd/contrib/device-tree/src/arm64/amd/
H A Damd-overdrive.dts55 pl022,hierarchy = <0>;
H A Dhusky.dts74 pl022,hierarchy = <0>;
H A Damd-overdrive-rev-b1.dts78 pl022,hierarchy = <0>;
H A Damd-overdrive-rev-b0.dts74 pl022,hierarchy = <0>;
/f-stack/freebsd/contrib/device-tree/Bindings/clock/ti/
H A Dclockdomain.txt11 hardware hierarchy.
/f-stack/freebsd/contrib/device-tree/src/arm64/broadcom/northstar2/
H A Dns2-svk.dts116 pl022,hierarchy = <0>;
140 pl022,hierarchy = <0>;
/f-stack/dpdk/doc/guides/nics/
H A Dmvpp2.rst591 Internally TM is represented by a hierarchy (tree) of nodes.
594 MVPP2 PMD supports two level hierarchy where level 0 represents ports and level 1 represents tx que…
608 After hierarchy is complete it can be committed.
621 - Maximum number of levels in hierarchy is 2
622 - Currently dynamic change of a hierarchy is not supported
735 8. Commit hierarchy:
739 testpmd> port tm hierarchy commit 0 no
744 no - Do not flush TM hierarchy if commit fails.

123