Searched full:nodes (Results 1 – 25 of 814) sorted by relevance
12345678910>>...33
| /Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 17 which is an administrative mechanism for restricting the nodes from which
40 allocations across all nodes with "sufficient" memory, so as
164 an optional set of nodes. The mode determines the behavior of the
166 and the optional set of nodes can be viewed as the arguments to the
188 does not use the optional set of nodes.
190 It is an error for the set of nodes specified for this policy to
195 nodes specified by the policy. Memory will be allocated from
202 allocation fails, the kernel will search other nodes, in order
222 page granularity, across the nodes specified in the policy.
227 Interleave mode indexes the set of nodes specified by the
[all …]
|
| D | numaperf.rst | 14 under different domains, or "nodes", based on locality and performance
16 are provided as memory only nodes. While memory only nodes do not provide
17 CPUs, they may still be local to one or more compute nodes relative to
18 other nodes. The following diagram shows one such example of two compute
19 nodes with local memory and a memory only node for each of compute node::
56 nodes' access characteristics share the same performance relative to other
57 linked initiator nodes. Each target within an initiator's access class,
63 nodes containing CPUs are considered.
76 These attributes apply only when accessed from nodes that have the
|
| /Documentation/devicetree/bindings/usb/ |
| D | usb-device.yaml | 17 Four types of device-tree nodes are defined: "host-controller nodes"
18 representing USB host controllers, "device nodes" representing USB devices,
19 "interface nodes" representing USB interfaces and "combined nodes"
32 description: Device nodes or combined nodes.
46 description: should be 1 for hub nodes with device nodes,
47 should be 2 for device nodes with interface nodes.
56 description: USB interface nodes.
63 description: Interface nodes.
|
| /Documentation/mm/ |
| D | numa.rst | 47 abstractions called "nodes". Linux maps the nodes onto the physical cells
49 architectures. As with physical cells, software nodes may contain 0 or more
51 "closer" nodes--nodes that map to closer cells--will generally experience
62 the emulation of additional nodes. For NUMA emulation, linux will carve up
63 the existing nodes--or the system memory for non-NUMA platforms--into multiple
64 nodes. Each emulated node will manage a fraction of the underlying cells'
74 an ordered "zonelist". A zonelist specifies the zones/nodes to visit when a
79 Because some nodes contain multiple zones containing different types of
85 from the same node before using remote nodes which are ordered by NUMA distance.
92 nodes' zones in the selected zonelist looking for the first zone in the list
[all …]
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-fsi.txt | 9 nodes.
10 - #size-cells = <0>; : Number of size cells in child nodes.
11 - child nodes : Nodes to describe busses off the I2C
18 - child nodes : Nodes to describe devices on the I2C
|
| /Documentation/devicetree/bindings/cpu/ |
| D | cpu-topology.txt | 20 For instance in a system where CPUs support SMT, "cpu" nodes represent all
22 In systems where SMT is not supported "cpu" nodes represent all cores present
25 CPU topology bindings allow one to associate cpu nodes with hierarchical groups
27 tree nodes.
32 The cpu nodes, as per bindings defined in [4], represent the devices that
35 A topology description containing phandles to cpu nodes that are not compliant
44 nodes are listed.
60 The cpu-map node's child nodes can be:
62 - one or more cluster nodes or
63 - one or more socket nodes in a multi-socket system
[all …]
|
| /Documentation/driver-api/md/ |
| D | md-cluster.rst | 54 node may write to those sectors. This is used when a new nodes
60 Each node has to communicate with other nodes when starting or ending
70 Normally all nodes hold a concurrent-read lock on this device.
75 Messages can be broadcast to all nodes, and the sender waits for all
76 other nodes to acknowledge the message before proceeding. Only one
87 informs other nodes that the metadata has
94 informs other nodes that a resync is initiated or
104 informs other nodes that a device is being added to
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
[all …]
|
| /Documentation/driver-api/acpi/ |
| D | scan_handlers.rst | 19 acpi_device objects are referred to as "device nodes" in what follows, but they
23 During ACPI-based device hot-remove device nodes representing pieces of hardware
27 initialization of device nodes, such as retrieving common configuration
48 where ids is the list of IDs of device nodes the given handler is supposed to
51 executed, respectively, after registration of new device nodes and before
52 unregistration of device nodes the handler attached to previously.
55 device nodes in the given namespace scope with the driver core. Then, it tries
72 callbacks from the scan handlers of all device nodes in the given namespace
74 nodes in that scope.
79 is the order in which they are matched against device nodes during namespace
|
| /Documentation/filesystems/ |
| D | ubifs-authentication.rst | 80 - *Index*: an on-flash B+ tree where the leaf nodes contain filesystem data
98 Basic on-flash UBIFS entities are called *nodes*. UBIFS knows different types
99 of nodes. Eg. data nodes (``struct ubifs_data_node``) which store chunks of file
100 contents or inode nodes (``struct ubifs_ino_node``) which represent VFS inodes.
101 Almost all types of nodes share a common header (``ubifs_ch``) containing basic
104 and some less important node types like padding nodes which are used to pad
108 as *wandering tree*, where only the changed nodes are re-written and previous
121 a dirty-flag which marks nodes that have to be persisted the next time the
126 on-flash filesystem structures like the index. On every commit, the TNC nodes
135 any changes (in form of inode nodes, data nodes etc.) between commits
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinctrl.yaml | 14 Pin controller devices should contain the pin configuration nodes that client
17 The contents of each of those pin configuration child nodes is defined
22 The pin configuration nodes need not be direct children of the pin controller
25 nodes, is again defined entirely by the binding for the individual pin
43 child nodes for individual pin group control.
|
| D | fsl,mxs-pinctrl.txt | 36 having these pins defined in several group nodes. It also means each of
50 and config nodes to identify a pin. The mux selection in the integer takes
56 - reg: Should be the index of the group nodes for same function. This property
57 is required only for group nodes, and should not be present in any config
58 nodes.
119 applied on all these pins. And config nodes mmc-cd-cfg and mmc-sck-cfg are
122 to be listed in the config nodes.
|
| /Documentation/devicetree/bindings/pwm/ |
| D | pwm-tipwmss.txt | 10 - address-cells: Specify the number of u32 entries needed in child nodes.
12 - size-cells: specify number of u32 entries needed to specify child nodes size
20 Also child nodes should also populated under PWMSS DT node.
33 /* child nodes go here */
46 /* child nodes go here */
57 /* child nodes go here */
|
| /Documentation/power/powercap/ |
| D | dtpm.rst | 39 The nodes of the tree are a virtual description aggregating the power
40 characteristics of the children nodes and their power limitations.
64 When the nodes are inserted in the tree, their power characteristics are propagated to the parents::
106 A root node is created and it is the parent of all the nodes. This
115 hierarchically. There is one root node, all intermediate nodes are
116 grouping the child nodes which can be intermediate nodes also or real
119 The intermediate nodes aggregate the power information and allows to
120 set the power limit given the weight of the nodes.
137 if it is not recommended for the user space, several nodes can have
170 allocate and link the different nodes of the tree.
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | marvell-pxa168.txt | 11 - #address-cells: must be 1 when using sub-nodes.
12 - #size-cells: must be 0 when using sub-nodes.
18 Sub-nodes:
21 Sub-nodes required properties:
|
| /Documentation/sphinx/ |
| D | automarkup.py | 7 from docutils import nodes
110 repl.append(nodes.Text(t[done:m.start()]))
120 repl.append(nodes.Text(t[done:]))
143 target_text = nodes.Text(match.group(0))
154 lit_text = nodes.literal(classes=['xref', 'c', 'c-func'])
203 target_text = nodes.Text(match.group(0))
214 lit_text = nodes.literal(classes=['xref', 'c', class_str[match.re]])
268 return nodes.Text(match.group(0))
283 # The nodes.literal test catches ``literal text``, its purpose is to
286 if not isinstance(node, nodes.Text) or isinstance(node.parent, nodes.literal):
[all …]
|
| D | rstFlatTable.py | 45 from docutils import nodes
94 class rowSpan(nodes.General, nodes.Element): pass # pylint: disable=C0103,C0321
95 class colSpan(nodes.General, nodes.Element): pass # pylint: disable=C0103,C0321
117 nodes.literal_block(self.block_text, self.block_text),
122 node = nodes.Element() # anonymous container for parsing
156 table = nodes.table()
157 tgroup = nodes.tgroup(cols=len(colwidths))
162 colspec = nodes.colspec(colwidth=colwidth)
176 thead = nodes.thead()
181 tbody = nodes.tbody()
[all …]
|
| /Documentation/devicetree/bindings/display/ti/ |
| D | ti,omap4-dss.txt | 17 Required nodes:
20 Optional nodes:
54 Optional nodes:
70 Optional nodes:
91 Optional nodes:
114 Optional nodes:
|
| D | ti,omap5-dss.txt | 17 Required nodes:
20 Optional nodes:
54 Optional nodes:
72 Optional nodes:
95 Optional nodes:
|
| /Documentation/ABI/stable/ |
| D | sysfs-devices-node | 5 Nodes that could be possibly become online at some point.
11 Nodes that are online.
17 Nodes that have regular memory.
23 Nodes that have one or more CPUs.
29 Nodes that have regular or high memory.
70 Distance between the node and all the other nodes
99 The node's relationship to other nodes for access class "Y".
106 nodes that have class "Y" access to this target node's
107 memory. CPUs and other memory initiators in nodes not in
123 nodes found in this access class's linked initiators.
[all …]
|
| /Documentation/devicetree/bindings/clock/ |
| D | st,nomadik.txt | 23 PLL nodes: these nodes represent the two PLLs on the system,
27 Required properties for the two PLL nodes:
34 HCLK nodes: these represent the clock gates on individual
38 Requires properties for the HCLK nodes:
|
| /Documentation/ABI/testing/ |
| D | sysfs-fs-ubifs | 8 This counter keeps track of the number of accesses of nodes
20 This counter keeps track of the number of accesses of nodes
32 This counter keeps track of the number of accesses of nodes
|
| /Documentation/driver-api/media/ |
| D | v4l2-intro.rst | 7 hardware: most devices have multiple ICs, export multiple device nodes in
18 creating V4L device nodes and video_buf for handling the video buffers
46 3) Creating V4L2 device nodes (/dev/videoX, /dev/vbiX and /dev/radioX)
61 \-V4L2 device nodes
75 driver sets the struct v4l2_device mdev field, sub-devices and video nodes
|
| /Documentation/arch/x86/x86_64/ |
| D | fake-numa-for-cpusets.rst | 13 you can create fake NUMA nodes that represent contiguous chunks of memory and
21 configuring fake nodes, see Documentation/arch/x86/x86_64/boot-options.rst.
27 you'll determine a better setup to minimize the number of nodes you have to deal
43 Documentation/admin-guide/cgroup-v1/cpusets.rst, you can assign fake nodes (i.e. contiguous memory
53 Now this cpuset, 'ddset', will only allowed access to fake nodes 0 and 1 for
57 available to them according to the fake nodes assigned as mems::
|
| /Documentation/devicetree/bindings/fsi/ |
| D | fsi.txt | 6 nodes to probed engines. This allows for fsi engines to expose non-probeable
11 FSI masters may require their own DT nodes (to describe the master HW itself);
15 Under the masters' nodes, we can describe the bus topology using nodes to
41 adding subordinate device tree nodes as children of FSI engines.
46 FSI master nodes declare themselves as such with the "fsi-master" compatible
52 Since the master nodes describe the top-level of the FSI topology, they also
95 use a single cell for address and size. Engine nodes represent the endpoint
|
| /Documentation/devicetree/bindings/net/pse-pd/ |
| D | pse-controller.yaml | 11 power over twisted pair/ethernet cable. The ethernet-pse nodes should be
24 0 on PSE nodes with only a single output and at least 1 on nodes
|
12345678910>>...33