Home
last modified time | relevance | path

Searched refs:node (Results 1 – 25 of 1669) sorted by relevance

12345678910>>...67

/Documentation/devicetree/bindings/
Dnuma.txt11 that comprise what is commonly known as a NUMA node.
12 Processor accesses to memory within the local NUMA node is generally faster
13 than processor accesses to memory outside of the local NUMA node.
14 DT defines interfaces that allow the platform to convey NUMA node
18 2 - numa-node-id
21 For the purpose of identification, each NUMA node is associated with a unique
22 token known as a node id. For the purpose of this binding
23 a node id is a 32-bit integer.
25 A device node is associated with a NUMA node by the presence of a
26 numa-node-id property which contains the node id of the device.
[all …]
/Documentation/ABI/stable/
Dsysfs-devices-node1 What: /sys/devices/system/node/possible
7 What: /sys/devices/system/node/online
13 What: /sys/devices/system/node/has_normal_memory
19 What: /sys/devices/system/node/has_cpu
25 What: /sys/devices/system/node/has_high_memory
32 What: /sys/devices/system/node/nodeX
37 information on node X such as what CPUs are local to the
38 node. Each file is detailed next.
40 What: /sys/devices/system/node/nodeX/cpumap
44 The node's cpumap.
[all …]
Dsysfs-bus-firewire6 IEEE 1394 node device attributes.
7 Read-only. Mutable during the node device's lifetime.
15 The node's EUI-64 in the bus information block of
25 IEEE 1394 node device attribute.
26 Read-only. Mutable during the node device's lifetime.
30 Summary of all units present in an IEEE 1394 node.
32 version of each unit present in the node. Specifier_id
47 IEEE 1394 node device attribute.
49 Values: 1: The sysfs entry represents a local node (a controller card).
50 0: The sysfs entry represents a remote node.
[all …]
/Documentation/
Drbtree.txt65 struct rb_node node;
71 individual members may be accessed directly via rb_entry(node, type, member).
88 struct rb_node *node = root->rb_node;
90 while (node) {
91 struct mytype *data = container_of(node, struct mytype, node);
97 node = node->rb_left;
99 node = node->rb_right;
110 new node, then inserting the node and rebalancing ("recoloring") the tree.
113 location of the pointer on which to graft the new node. The new node also
114 needs a link to its parent node for rebalancing purposes.
[all …]
/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,bcm2835.txt5 Required root node properties:
9 Required root node properties:
13 Required root node properties:
18 Required root node properties:
22 Required root node properties:
26 Required root node properties:
30 Required root node properties:
34 Required root node properties:
38 Required root node properties:
42 Required root node properties:
[all …]
Dbrcm,bcm63138.txt7 Required root node property:
11 An optional Boot lookup table Device Tree node is required for secondary CPU
16 Required properties for the Boot lookup table node:
20 Optional properties for the primary CPU node:
23 Optional properties for the secondary CPU node:
56 Two nodes are required for software reboot: a timer node and a syscon-reboot node.
58 Timer node:
63 Syscon reboot node:
/Documentation/devicetree/bindings/cpu/
Dcpu-topology.txt39 2 - cpu-map node
42 The ARM/RISC-V CPU topology is defined within the cpu-map node, which is a direct
43 child of the cpus node and provides a container where the actual topology
46 - cpu-map node
51 cpu-map node.
53 Description: The cpu-map node is just a container node where its
58 The cpu-map node's parent node must be the cpus node.
60 The cpu-map node's child nodes can be:
67 The cpu-map node can only contain 4 types of child nodes:
69 - socket node
[all …]
/Documentation/admin-guide/
Dnumastat.rst5 /sys/devices/system/node/node*/numastat
10 numa_hit A process wanted to allocate memory from this node,
13 numa_miss A process wanted to allocate memory from another node,
14 but ended up with memory from this node.
16 numa_foreign A process wanted to allocate on this node,
19 local_node A process ran on this node and got memory from it.
21 other_node A process ran on this node and got memory from another node.
23 interleave_hit Interleaving wanted to allocate from this node
/Documentation/vm/
Dswap_numa.rst4 Automatically bind swap device to numa node
7 If the system has more than one swap device and swap device has the node
17 for swap devices. e.g. on a 2 node machine, assume 2 swap devices swapA and
18 swapB, with swapA attached to node 0 and swapB attached to node 1, are going
24 Then node 0 will use the two swap devices in the order of swapA then swapB and
25 node 1 will use the two swap devices in the order of swapB then swapA. Note
28 A more complex example on a 4 node machine. Assume 6 swap devices are going to
29 be swapped on: swapA and swapB are attached to node 0, swapC is attached to
30 node 1, swapD and swapE are attached to node 2 and swapF is attached to node3.
40 Then node 0 will use them in the order of::
[all …]
Dnuma.rst57 For some architectures, such as x86, Linux will "hide" any node representing a
59 that cell to a node representing a cell that does have memory. Thus, on
61 a given node will see the same local memory access times and bandwidth.
66 nodes. Each emulated node will manage a fraction of the underlying cells'
72 For each node with memory, Linux constructs an independent memory management
77 selected zone/node cannot satisfy the allocation request. This situation,
83 fall back to the same zone type on a different node, or to a different zone
84 type on the same node. This is an important consideration because some zones,
87 from the same node before using remote nodes which are ordered by NUMA distance.
90 node to which the CPU that executes the request is assigned. Specifically,
[all …]
/Documentation/devicetree/bindings/regulator/
Disl9305.txt7 - regulators: A node that houses a sub-node for each regulator within the
8 device. Each sub-node is identified using the node's name, with valid
9 values being "dcd1", "dcd2", "ldo1" and "ldo2". The content of each sub-node
11 - VINDCD1-supply: A phandle to a regulator node supplying VINDCD1.
12 VINDCD2-supply: A phandle to a regulator node supplying VINDCD2.
13 VINLDO1-supply: A phandle to a regulator node supplying VINLDO1.
14 VINLDO2-supply: A phandle to a regulator node supplying VINLDO2.
/Documentation/sphinx/
Dkfigure.py104 node = nodes.literal_block(data, data)
105 return node
116 def pass_handle(self, node): # pylint: disable=W0613 argument
338 def visit_kernel_image(self, node): # pylint: disable=W0613 argument
343 img_node = node[0]
369 node = kernel_image('', image_node)
370 return [node]
375 def visit_kernel_figure(self, node): # pylint: disable=W0613 argument
380 img_node = node[0][0]
406 node = kernel_figure('', figure_node)
[all …]
Dautomarkup.py36 def markup_funcs(docname, app, node): argument
38 t = node.astext()
93 for node in para.traverse(nodes.Text):
94 if not isinstance(node.parent, nodes.literal):
95 node.parent.replace(node, markup_funcs(name, app, node))
/Documentation/devicetree/bindings/pinctrl/
Dcnxt,cx92755-pinctrl.txt14 - gpio-controller: Marks the device node as a GPIO controller.
19 For example, the following is the bare minimum node:
28 As a pin controller device, in addition to the required properties, this node
36 Each pin configuration node is a sub-node of the pin controller node and is a
42 "pin configuration node".
46 A pin group node specifies the desired pin mux for an arbitrary number of
47 pins. The name of the pin group node is optional and not used.
49 A pin group node only affects the properties specified in the node, and has no
52 The pin group node accepts a subset of the generic pin config properties. For
59 configured by this node. The format of a pin name string is "GP_xy", where x
[all …]
Drenesas,rzn1-pinctrl.txt1 Renesas RZ/N1 SoC Pinctrl node description.
3 Pin controller node
28 The child nodes of the pin controller node describe a pin multiplexing
32 A pin multiplexing sub-node describes how to configure a set of
34 A single sub-node may define several pin configurations.
38 The allowed generic formats for a pin multiplexing sub-node are the
41 node-1 {
46 node-2 {
47 sub-node-1 {
52 sub-node-2 {
[all …]
Dfsl,imx-pinctrl.txt12 phrase "pin configuration node".
14 Freescale IMX pin configuration node is a node of a group of pins which can be
15 used for a specific device or function. This node represents both mux and config
24 Required properties for pin configuration node:
46 1. We have pin function node defined under iomux controller node to represent
48 2. The pin configuration node intends to work on a specific function should
49 to be defined under that specific function node.
50 The function node's name should represent well about what function
51 this group of pins in this pin configuration node are working on.
52 3. The driver can use the function node's name and pin configuration node's
[all …]
/Documentation/devicetree/bindings/powerpc/nintendo/
Dgamecube.txt5 1) The "flipper" node
7 This node represents the multi-function "Flipper" chip, which packages
14 1.a) The Video Interface (VI) node
25 1.b) The Processor Interface (PI) node
35 1.b.i) The "Flipper" interrupt controller node
38 The node for the "Flipper" interrupt controller must be placed under
39 the PI node.
45 1.c) The Digital Signal Procesor (DSP) node
56 1.c.i) The Auxiliary RAM (ARAM) node
60 The ARAM node must be placed under the DSP node.
[all …]
Dwii.txt5 0) The root node
7 This node represents the Nintendo Wii video game console.
14 1) The "hollywood" node
16 This node represents the multi-function "Hollywood" chip, which packages
23 1.a) The Video Interface (VI) node
34 1.b) The Processor Interface (PI) node
44 1.b.i) The "Flipper" interrupt controller node
47 The node for the "Flipper" interrupt controller must be placed under
48 the PI node.
56 1.c) The Digital Signal Procesor (DSP) node
[all …]
/Documentation/devicetree/bindings/hwlock/
Dhwlock.txt25 - hwlocks: List of phandle to a hwlock provider node and an
37 1. Example of a node using a single specific hwlock:
39 The following example has a node requesting a hwlock in the bank defined by
40 the node hwlock1. hwlock1 is a hwlock provider with an argument specifier
43 node {
49 2. Example of a node using multiple specific hwlocks:
51 The following example has a node requesting two hwlocks, a hwlock within
52 the hwlock device node 'hwlock1' with #hwlock-cells value of 1, and another
53 hwlock within the hwlock device node 'hwlock2' with #hwlock-cells value of 2.
55 node {
/Documentation/driver-api/md/
Dmd-cluster.rst12 Separate write-intent-bitmaps are used for each cluster node.
13 The bitmaps record all writes that may have been started on that node,
24 one node writes to any given block at a time, so a write request will
31 one node doesn't read from a location where another node (or the same
32 node) is writing.
43 The bm_lockres protects individual node bitmaps. They are named in
44 the form bitmap000 for node 1, bitmap001 for node 2 and so on. When a
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
48 subsystem. Since DLM starts node count from one and bitmap slots
[all …]
/Documentation/devicetree/bindings/csky/
Dcpus.txt6 the "cpus" node, which in turn contains a number of subnodes (ie "cpu")
9 Only SMP system need to care about the cpus node and single processor
10 needn't define cpus node at all.
13 cpus and cpu node bindings definition
16 - cpus node
20 The node name must be "cpus".
22 A cpus node must define the following properties:
33 - cpu node
/Documentation/admin-guide/mm/
Dnumaperf.rst8 node. These disparate memory ranges may share some characteristics, such
14 characteristics. Some memory may share the same node as a CPU, and others
18 nodes with local memory and a memory only node for each of compute node::
29 A "memory initiator" is a node containing one or more devices such as
31 A "memory target" is a node containing one or more physical address
47 # symlinks -v /sys/devices/system/node/nodeX/access0/targets/
48 relative: /sys/devices/system/node/nodeX/access0/targets/nodeY -> ../../nodeY
50 # symlinks -v /sys/devices/system/node/nodeY/access0/initiators/
51 relative: /sys/devices/system/node/nodeY/access0/initiators/nodeX -> ../../nodeX
63 Applications may wish to consider which node they want their memory to
[all …]
/Documentation/devicetree/bindings/net/
Dfsl-enetc.txt11 to parent node bindings.
18 In this case, the ENETC node should include a "mdio" sub-node
19 that in turn should contain the "ethernet-phy" node describing the
31 - mdio : "mdio" node, defined in mdio.txt.
33 - ethernet-phy : "ethernet-phy" node, defined in phy.txt.
54 In this case, the mdio node should be defined as another PCIe
55 endpoint node, at the same level with the ENETC port nodes.
61 to parent node bindings.
89 In this case, the ENETC port node defines a fixed link connection,
94 - fixed-link : "fixed-link" node, defined in "fixed-link.txt".
/Documentation/ABI/testing/
Dppc-memtrace14 you want removed from each NUMA node to this file - it must be
16 from each NUMA node in the kernel mappings and the following
18 removed from each node, the following files are created. To
22 What: /sys/kernel/debug/powerpc/memtrace/<node-id>
27 from the specific NUMA node.
29 What: /sys/kernel/debug/powerpc/memtrace/<node-id>/size
33 Description: This contains the size of the memory removed from the node.
35 What: /sys/kernel/debug/powerpc/memtrace/<node-id>/start
41 What: /sys/kernel/debug/powerpc/memtrace/<node-id>/trace
/Documentation/firmware-guide/acpi/dsd/
Ddata-node-references.rst17 extension node which is referred to by the key shall lie directly under the
19 extension node.
21 The keys in the hierarchical data nodes shall consist of the name of the node,
22 "@" character and the number of the node in hexadecimal notation (without pre-
25 the node.
27 In case a hierarchical data extensions node has no numerical value, then the
38 hierarchical data extension key "node@1" referring to the NOD1 object
40 the ANOD object which is also the final target node of the reference.
48 Package () { "node@0", "NOD0" },
49 Package () { "node@1", "NOD1" },
[all …]

12345678910>>...67