Searched full:cluster (Results 1 – 25 of 96) sorted by relevance
1234
| /Documentation/arch/arm/ |
| D | cluster-pm-race-avoidance.rst | 2 Cluster-wide Power-up/power-down race avoidance algorithm
6 cluster setup and teardown operations and to manage hardware coherency
29 cluster-level operations are only performed when it is truly safe to do
34 are not immediately enabled when a cluster powers up. Since enabling or
38 power-down and power-up at the cluster level.
48 Each cluster and CPU is assigned a state, as follows:
67 The CPU or cluster is not coherent, and is either powered off or
71 The CPU or cluster has committed to moving to the UP state.
76 The CPU or cluster is active and coherent at the hardware
81 The CPU or cluster has committed to moving to the DOWN
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-ocfs2 | 14 covers how ocfs2 uses distributed locking between cluster
18 cluster nodes can interoperate if they have an identical
34 the available plugins to support ocfs2 cluster operation.
35 A cluster plugin is required to use ocfs2 in a cluster.
38 * 'o2cb' - The classic o2cb cluster stack that ocfs2 has
40 * 'user' - A plugin supporting userspace cluster software
54 cluster plugin is currently in use by the filesystem.
62 the cluster stack in use. The contents may change
63 when all filesystems are unmounted and the cluster stack
71 of current ocfs2 cluster stack. This value is set by
[all …]
|
| /Documentation/devicetree/bindings/cpufreq/ |
| D | apple,cluster-cpufreq.yaml | 4 $id: http://devicetree.org/schemas/cpufreq/apple,cluster-cpufreq.yaml#
7 title: Apple SoC cluster cpufreq device
13 Apple SoCs (e.g. M1) have a per-cpu-cluster DVFS controller that is part of
14 the cluster management register block. This binding uses the standard
23 - apple,t8103-cluster-cpufreq
24 - apple,t8112-cluster-cpufreq
25 - const: apple,cluster-cpufreq
27 - const: apple,t6000-cluster-cpufreq
28 - const: apple,t8103-cluster-cpufreq
29 - const: apple,cluster-cpufreq
[all …]
|
| /Documentation/devicetree/bindings/phy/ |
| D | phy-mvebu.txt | 23 Armada 375 USB cluster
27 controller. The USB cluster control register allows to manage common
32 - compatible: "marvell,armada-375-usb-cluster"
33 - reg: Should contain usb cluster register location and length.
38 usbcluster: usb-cluster@18400 {
39 compatible = "marvell,armada-375-usb-cluster";
|
| /Documentation/devicetree/bindings/arm/tegra/ |
| D | nvidia,tegra-ccplex-cluster.yaml | 4 $id: http://devicetree.org/schemas/arm/tegra/nvidia,tegra-ccplex-cluster.yaml#
7 title: NVIDIA Tegra CPU COMPLEX CLUSTER area
16 The Tegra CPU COMPLEX CLUSTER area contains memory-mapped
25 - nvidia,tegra186-ccplex-cluster
26 - nvidia,tegra234-ccplex-cluster
47 compatible = "nvidia,tegra234-ccplex-cluster";
|
| /Documentation/devicetree/bindings/net/dsa/ |
| D | dsa.yaml | 28 A two element list indicates which DSA cluster, and position within the
29 cluster a switch takes. <0 0> is cluster 0, switch 0. <0 1> is cluster 0,
30 switch 1. <1 0> is cluster 1, switch 0. A switch not part of any cluster
|
| /Documentation/networking/ |
| D | tipc.rst | 11 designed for intra-cluster communication. It can be configured to transmit
20 - Cluster wide IPC service
23 transmitting data between cluster nodes? Where you yourself determine the
44 The service tracking mechanism can also be used for Cluster Topology Tracking,
45 i.e., subscribing for availability/non-availability of cluster nodes.
47 Likewise, the service tracking mechanism can be used for Cluster Connectivity
49 cluster nodes.
66 Communication between any two nodes in a cluster is maintained by one or two
70 - Cluster Scalability
79 Neighbor Node Discovery in the cluster is done by Ethernet broadcast or UDP
[all …]
|
| /Documentation/driver-api/md/ |
| D | md-cluster.rst | 2 MD Cluster
5 The cluster MD is a shared-device RAID for a cluster, it supports
12 Separate write-intent-bitmaps are used for each cluster node.
45 node joins the cluster, it acquires the lock in PW mode and it stays
46 so during the lifetime the node is part of the cluster. The lock
55 joins the cluster.
128 The DLM LVB is used to communicate within nodes of the cluster. There
145 acknowledged by all nodes in the cluster. The BAST of the resource
216 When a node fails, the DLM informs the cluster with the slot
217 number. The node starts a cluster recovery thread. The cluster
[all …]
|
| D | index.rst | 10 md-cluster
|
| /Documentation/filesystems/ |
| D | gfs2.rst | 7 GFS2 is a cluster file system. It allows a cluster of computers to
13 on one machine show up immediately on all other machines in the cluster.
25 lock_dlm depends on user space cluster management systems found
34 The gfs2-utils package is required on all cluster nodes and, for lock_dlm, you
|
| D | ceph.rst | 25 In contrast to cluster filesystems like GFS, OCFS2, and GPFS that rely
33 (with some minimal coordination from a cluster monitor), making the
49 from a small cluster of just a few nodes to many hundreds, without
109 used instead of an IP address and the cluster FSID can be left out
120 configuration file if available. Note that, the cluster FSID (passed as part
128 Monitor address to the cluster. This is used to bootstrap the
129 connection to the cluster. Once connection is established, the
132 fsid=cluster-id
133 FSID of the cluster (from `ceph fsid` command).
204 * clean: client reconnects to the ceph cluster automatically when it
|
| D | ocfs2.rst | 7 OCFS2 is a general purpose extent based shared disk cluster file
56 intr (*) Allow signals to interrupt cluster operations.
57 nointr Do not allow signals to interrupt cluster
90 localflocks This disables cluster aware flock.
106 coherency=full (*) Disallow concurrent O_DIRECT writes, cluster inode
108 therefore full cluster coherency is guaranteed even
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | samsung-wdt.yaml | 48 samsung,cluster-index:
51 Index of CPU cluster on which watchdog is running (in case of Exynos850
101 samsung,cluster-index:
104 - samsung,cluster-index
113 samsung,cluster-index: false
|
| /Documentation/devicetree/bindings/cpu/ |
| D | cpu-topology.txt | 13 - cluster
62 - one or more cluster nodes or
70 - cluster node
76 The nodes describing the CPU topology (socket/cluster/core/thread) can
87 (ie socket/cluster/core/thread) (where N = {0, 1, ...} is the node number; nodes
95 3 - socket/cluster/core/thread node bindings
98 Bindings for socket/cluster/cpu/thread nodes are defined as follows:
114 A socket node's child nodes must be one or more cluster nodes.
118 - cluster node
121 per cluster. A system can contain several layers of
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | intel_uncore_frequency_scaling.rst | 66 of mesh partitions. This partition is called fabric cluster.
69 be placed in the same fabric cluster. Benefit of fabric cluster is that it
74 fabric cluster level.
80 To represent controls at fabric cluster level in addition to the
95 This attribute is used to get the fabric cluster id of this instance.
107 cluster is affected in that package and die. For example: user changes
114 Support for "current_freq_khz" is available only at each fabric cluster
|
| /Documentation/filesystems/ext4/ |
| D | bigalloc.rst | 18 megabyte range, it might make sense to set a cluster size of 1 megabyte.
25 The administrator can set a block cluster size at mkfs time (which is
29 128MiB); however, the minimum allocation unit becomes a cluster, not a
|
| /Documentation/devicetree/bindings/arm/marvell/ |
| D | ap80x-system-controller.txt | 24 - 0: reference clock of CPU cluster 0
25 - 1: reference clock of CPU cluster 1
157 Cluster clocks:
160 Device Tree Clock bindings for cluster clock of Marvell
161 AP806/AP807. Each cluster contain up to 2 CPUs running at the same
171 (one per cluster)
173 - reg: register range associated with the cluster clocks
|
| /Documentation/devicetree/bindings/power/ |
| D | mti,mips-cpc.yaml | 7 title: MIPS Cluster Power Controller
10 Defines a location of the MIPS Cluster Power Controller registers.
|
| /Documentation/devicetree/bindings/soc/bcm/ |
| D | brcm,bcm23550-cdc.yaml | 7 title: Broadcom BCM23550 Cluster Dormant Control
10 The Cluster Dormant Control block keeps the CPU in idle state. A command
|
| /Documentation/admin-guide/perf/ |
| D | qcom_l2_pmu.rst | 7 own PMU. Each cluster has one or more CPUs associated with it.
29 consisting of one CPU per cluster which will be used to handle all the PMU
30 events on that cluster.
|
| D | hisi-pmu.rst | 10 The HiSilicon SoC encapsulates multiple CPU and IO dies. Each CPU cluster
12 called Super CPU cluster (SCCL) and is made up of 6 CCLs. Each SCCL has
58 1. L3C PMU supports filtering by core/thread within the cluster which can be
63 This will only count the operations from core/thread 0 and 1 in this cluster.
73 This will only count the read operations in this cluster.
|
| /Documentation/driver-api/media/ |
| D | v4l2-controls.rst | 507 In that case you need to 'cluster' them:
526 cluster is set (or 'gotten', or 'tried'), only the control ops of the first
541 struct v4l2_ctrl *mute = ctrl->cluster[AUDIO_CL_MUTE];
557 ctrl == ctrl->cluster[AUDIO_CL_VOLUME] == state->audio_cluster[AUDIO_CL_VOLUME]
558 ctrl->cluster[AUDIO_CL_MUTE] == state->audio_cluster[AUDIO_CL_MUTE]
560 In practice using cluster arrays like this becomes very tiresome. So instead
566 /* audio cluster */
571 The anonymous struct is used to clearly 'cluster' these two control pointers,
583 Note that controls in a cluster may be NULL. For example, if for some
586 cluster of 2 controls, of which only 1 is actually instantiated. The
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | qcom,msm8996-apcc.yaml | 13 Qualcomm CPU clock controller for MSM8996 CPUs, clock 0 is for Power cluster
14 and clock 1 is for Perf cluster.
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | ti,k3-r5f-rproc.yaml | 14 processor subsystems/clusters (R5FSS). The dual core cluster can be used
28 representing the cluster, with a pair of child DT nodes representing
67 ti,cluster-mode:
70 Configuration Mode for the Dual R5F cores within the R5F cluster.
233 ti,cluster-mode:
246 ti,cluster-mode:
256 ti,cluster-mode:
304 ti,cluster-mode = <1>;
|
| /Documentation/devicetree/bindings/sound/ |
| D | apple,mca.yaml | 38 One interrupt per each cluster
51 listed in groups of four per cluster, and within the group they are given
82 Names for the DMA channels: 'tx'/'rx', then cluster number, then 'a'/'b'
|
1234