Searched full:cluster (Results 1 – 25 of 74) sorted by relevance
123
| /Documentation/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 …]
|
| D | debugfs-hisi-hpre | 1 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/regs
4 Description: Dump debug registers from the HPRE cluster.
7 What: /sys/kernel/debug/hisi_hpre/<bdf>/cluster[0-3]/cluster_ctrl
10 Description: Write the HPRE core selection in the cluster into this file,
|
| /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.
29 - description: Primary PLL clock for power cluster (little)
30 - description: Primary PLL clock for perf cluster (big)
31 - description: Alternate PLL clock for power cluster (little)
32 - description: Alternate PLL clock for perf cluster (big)
|
| /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/filesystems/ |
| D | gfs2.rst | 7 https://fedorahosted.org/cluster/wiki/HomePage
9 GFS is a cluster file system. It allows a cluster of computers to
15 on one machine show up immediately on all other machines in the cluster.
27 Lock_dlm depends on user space cluster management systems found
38 and write a cluster.conf as per the documentation. For F17 and above
|
| D | erofs.rst | 79 cluster for further reading. It still does
225 |-> cluster <-|-> cluster <-|-> cluster <-|-> cluster <-|-> cluster <-|
233 |-> cluster <-|-> cluster <-|-> cluster <-|
236 Currently each on-disk physical cluster can contain 4KB (un)compressed data
237 at most. For each logical cluster, there is a corresponding on-disk index to
238 describe its cluster type, physical cluster address, etc.
|
| 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
|
| D | gfs2-uevents.rst | 42 nodes in the cluster to mount the filesystem.
57 cluster. For this reason the ONLINE uevent was used when adding a new
87 able to join the cluster.
|
| 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
172 * clean: client reconnects to the ceph cluster automatically when it
|
| /Documentation/devicetree/bindings/net/dsa/ |
| D | dsa.yaml | 29 A two element list indicates which DSA cluster, and position within the
30 cluster a switch takes. <0 0> is cluster 0, switch 0. <0 1> is cluster 0,
31 switch 1. <1 0> is cluster 1, switch 0. A switch not part of any cluster
|
| /Documentation/devicetree/bindings/arm/ |
| D | rtsm-dcscb.txt | 1 ARM Dual Cluster System Configuration Block
4 The Dual Cluster System Configuration Block (DCSCB) provides basic
6 the Dual Cluster System implemented by the Real-Time System Model (RTSM).
|
| D | arm-dsu-pmu.txt | 5 form a multicore cluster. The PMU enables to gather various statistics on
|
| /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/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/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
149 Cluster clocks:
152 Device Tree Clock bindings for cluster clock of Marvell
153 AP806/AP807. Each cluster contain up to 2 CPUs running at the same
163 (one per cluster)
165 - reg: register range associated with the cluster clocks
|
| /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/power/ |
| D | mti,mips-cpc.yaml | 7 title: MIPS Cluster Power Controller
10 Defines a location of the MIPS Cluster Power Controller registers.
|
| /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.
|
| /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/cpufreq/ |
| D | cpufreq-qcom-hw.txt | 45 Example 1: Dual-cluster, Quad-core per cluster. CPUs within a cluster switch
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | ti,k3-r5f-rproc.yaml | 14 processor subsystems/clusters (R5FSS). The dual core cluster can be used
21 representing the cluster, with a pair of child DT nodes representing
56 ti,cluster-mode:
60 Configuration Mode for the Dual R5F cores within the R5F cluster.
238 ti,cluster-mode = <1>;
|
| /Documentation/driver-api/thermal/ |
| D | cpu-idle-cooling.rst | 48 belong to the same cluster, with a duration greater than the cluster
63 cpufreq. Ideally, if all CPUs belonging to the same cluster, inject
64 their idle cycles synchronously, the cluster can reach its power down
|
| /Documentation/devicetree/bindings/thermal/ |
| D | nvidia,tegra186-bpmp-thermal.txt | 4 interface that is used to read system temperatures, including CPU cluster
|
123