Searched full:array (Results 1 – 25 of 993) sorted by relevance
12345678910>>...40
| /Documentation/admin-guide/ |
| D | md.rst | 22 or, to assemble a partitionable array::
44 level of the RAID array
92 If a raid5 or raid6 array is both dirty and degraded, it could have
98 For this reason, md will normally refuse to start such an array. This
99 requires the sysadmin to take action to explicitly start the array
104 This option is not really available if the array has the root
106 array, md supports a module parameter ``start_dirty_degraded`` which,
131 An array is ``created`` by writing appropriate superblocks to all
138 An array should be created by a user-space tool. This will write
139 superblocks to all devices. It will usually mark the array as
[all …]
|
| /Documentation/core-api/ |
| D | assoc_array.rst | 2 Generic Associative Array Implementation
8 This associative array implementation is an object container with the following
18 2. Objects do not need to contain linkage blocks for use by the array. This
20 Rather, the array is made up of metadata blocks that point to objects.
22 3. Objects require index keys to locate them within the array.
25 already in the array will replace the old object.
32 7. Index keys can include a hash to scatter objects throughout the array.
34 8. The array can iterated over. The objects will not necessarily come out in
37 9. The array can be iterated over while it is being modified, provided the
43 10. Objects in the array can be looked up by means of their index key.
[all …]
|
| /Documentation/devicetree/bindings/usb/ |
| D | brcm,usb-pinmap.yaml | 27 description: Array of one or two GPIO pins used for input signals.
30 $ref: /schemas/types.yaml#/definitions/string-array
31 description: Array of input signal names, one per gpio in in-gpios.
34 $ref: /schemas/types.yaml#/definitions/uint32-array
35 description: Array of enable and mask pairs, one per gpio in-gpios.
39 description: Array of one GPIO pin used for output signals.
42 $ref: /schemas/types.yaml#/definitions/string-array
43 description: Array of output signal names, one per gpio in out-gpios.
46 $ref: /schemas/types.yaml#/definitions/uint32-array
47 description: Array of enable, value, changed and clear masks, one
|
| D | gr-udc.txt | 21 - epobufsizes : Array of buffer sizes for OUT endpoints when they differ
22 from the default size of 1024. The array is indexed by the OUT endpoint
25 only for as many endpoints as the array contains.
27 - epibufsizes : Array of buffer sizes for IN endpoints when they differ
28 from the default size of 1024. The array is indexed by the IN endpoint
31 only for as many endpoints as the array contains.
|
| /Documentation/bpf/ |
| D | map_array.rst | 12 ``BPF_MAP_TYPE_ARRAY`` and ``BPF_MAP_TYPE_PERCPU_ARRAY`` provide generic array
14 of constant size. The size of the array is defined in ``max_entries`` at
15 creation time. All array elements are pre-allocated and zero initialized when
18 stored can be of any size, however, all array elements are aligned to 8
24 memory are allocated to store all array values, starting on the second page,
42 Array elements can be retrieved using the ``bpf_map_lookup_elem()`` helper.
43 This helper returns a pointer into the array element, so to avoid data races
54 Array elements can be updated using the ``bpf_map_update_elem()`` helper.
59 Since the array is of constant size, ``bpf_map_delete_elem()`` is not supported.
60 To clear an array element, you may use ``bpf_map_update_elem()`` to insert a
[all …]
|
| /Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 7 may become inconsistent with data on other member disks. If the array is also
10 array or using it is as degraded - data calculated from parity for array blocks
13 this, md by default does not allow starting a dirty degraded array.
21 contents. PPL recovery is also performed when starting an array after an
23 the array. Because of this, using write-intent bitmap and PPL together is not
28 array member drives in the metadata area, on the parity drive of a particular
30 reduced by up to 30%-40% but it scales with the number of drives in the array
44 There is a limitation of maximum 64 disks in the array for PPL. It allows to
|
| D | raid5-cache.rst | 9 3.4) has a new option '--write-journal' to create array with cache. Please
10 refer to mdadm manual for details. By default (RAID array starts), the cache is
19 In both modes, all writes to the array will hit cache disk first. This means
25 This mode mainly fixes the 'write hole' issue. For RAID 4/5/6 array, an unclean
29 unclean shutdown. We call an array degraded if it has inconsistent data. MD
30 tries to resync the array to bring it back to normal state. But before the
32 corruption in the RAID array. This problem is called 'write hole'.
37 shutdown even the array is degraded. Thus the cache can close the 'write hole'.
41 doesn't cause data loss. Of course cache disk failure means the array is
68 The memory cache size has performance impact for the array. It's recommended
|
| /Documentation/scsi/ |
| D | hpsa.rst | 4 HPSA - Hewlett Packard Smart Array driver
7 This file describes the hpsa SCSI driver for HP Smart Array controllers.
9 Smart Array controllers. The hpsa driver is a SCSI driver, while the
19 - Smart Array P212
20 - Smart Array P410
21 - Smart Array P410i
22 - Smart Array P411
23 - Smart Array P812
24 - Smart Array P712m
25 - Smart Array P711m
[all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | pinmux-node.yaml | 50 For cases like this, the pin controller driver may use pinctrl-pin-array helper
58 pinctrl-pin-array = <
75 The index for pinctrl-pin-array must relate to the hardware for the pinctrl
88 settings represented as a single integer or an array of integers.
90 The pinmux property accepts an array of pinmux groups, each of them describing
110 - $ref: /schemas/types.yaml#/definitions/uint32-array
111 - $ref: /schemas/types.yaml#/definitions/string-array
118 $ref: /schemas/types.yaml#/definitions/string-array
128 $ref: /schemas/types.yaml#/definitions/uint32-array
130 pinctrl-pin-array:
[all …]
|
| D | pinctrl-single.yaml | 76 $ref: /schemas/types.yaml#/definitions/phandle-array
110 Array of pins as described in pinmux-node.yaml for pinctrl-pin-array
111 $ref: /schemas/types.yaml#/definitions/uint32-array
115 $ref: /schemas/types.yaml#/definitions/uint32-array
123 $ref: /schemas/types.yaml#/definitions/uint32-array
132 $ref: /schemas/types.yaml#/definitions/uint32-array
141 $ref: /schemas/types.yaml#/definitions/uint32-array
148 $ref: /schemas/types.yaml#/definitions/uint32-array
155 $ref: /schemas/types.yaml#/definitions/uint32-array
164 $ref: /schemas/types.yaml#/definitions/uint32-array
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-subdev-g-routing.rst | 57 ``routes`` array allocated by userspace. It is set by applications for both
63 routes that the application stored in the ``routes`` array. For both ioctls, it
71 the ``routes`` array. In this case, the ``routes`` array is filled by the kernel
75 ``VIDIOC_SUBDEV_G_ROUTING`` call with a large enough ``routes`` array.
95 - The length of the array (as in memory reserved for the array)
98 - Array of struct :c:type:`v4l2_subdev_route` entries
101 - Number of entries of the routes array
105 the array to zero.
135 the array to zero.
|
| /Documentation/devicetree/bindings/arm/ |
| D | vexpress-config.yaml | 35 $ref: /schemas/types.yaml#/definitions/uint32-array
53 $ref: /schemas/types.yaml#/definitions/uint32-array
71 $ref: /schemas/types.yaml#/definitions/uint32-array
89 $ref: /schemas/types.yaml#/definitions/uint32-array
117 $ref: /schemas/types.yaml#/definitions/uint32-array
123 $ref: /schemas/types.yaml#/definitions/uint32-array
148 $ref: /schemas/types.yaml#/definitions/uint32-array
169 $ref: /schemas/types.yaml#/definitions/uint32-array
190 $ref: /schemas/types.yaml#/definitions/uint32-array
211 $ref: /schemas/types.yaml#/definitions/uint32-array
[all …]
|
| /Documentation/mm/ |
| D | memory-model.rst | 38 In the FLATMEM memory model, there is a global `mem_map` array that
40 have entries in the `mem_map` array. The `struct page` objects
43 To allocate the `mem_map` array, architecture specific setup code should
44 call :c:func:`free_area_init` function. Yet, the mappings array is not
48 An architecture may free parts of the `mem_map` array that do not cover the
55 `mem_map` array.
72 array of struct pages. However, it is stored with some other magic
87 The `mem_section` objects are arranged in a two-dimensional array
88 called `mem_sections`. The size and placement of this array depend
93 array is static and has `NR_MEM_SECTIONS` rows. Each row holds a
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-led-multicolor | 7 The multi_index array, when read, will output the LED colors
8 as an array of strings as they are indexed in the
19 This file contains array of integers. Order of components is
20 described by the multi_index array. The maximum intensity should
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | ti,pru-consumer.yaml | 25 $ref: /schemas/types.yaml#/definitions/phandle-array
33 $ref: /schemas/types.yaml#/definitions/string-array
42 $ref: /schemas/types.yaml#/definitions/uint32-array
48 array of values for the GP_MUX_SEL under PRUSS_GPCFG register for a PRU.
53 same slice in the associative array. If the array size is smaller than
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-ioc-enum-links.rst | 42 If the ``pads`` field is not NULL, the driver fills the ``pads`` array
43 with information about the entity's pads. The array must have enough
47 If the ``links`` field is not NULL, the driver fills the ``links`` array
48 with information about the entity's outbound links. The array must have
70 - Pointer to a pads array allocated by the application. Ignored if
75 - Pointer to a links array allocated by the application. Ignored if
81 the array to zero.
107 the array to zero.
134 the array to zero.
|
| /Documentation/devicetree/bindings/sound/ |
| D | cirrus,madera.yaml | 44 MADERA_INMODE_xxx. If the array is shorter than the number
46 $ref: /schemas/types.yaml#/definitions/uint32-array
56 Mono bit for each output, maximum of six cells if the array
58 $ref: /schemas/types.yaml#/definitions/uint32-array
78 $ref: /schemas/types.yaml#/definitions/uint32-array
92 $ref: /schemas/types.yaml#/definitions/uint32-array
104 $ref: /schemas/types.yaml#/definitions/uint32-array
114 $ref: /schemas/types.yaml#/definitions/uint32-array
|
| D | omap-mcbsp.txt | 8 - reg: Register location and size, for OMAP4+ as an array:
11 - reg-names: Array of strings associated with the address space
12 - interrupts: Interrupt numbers for the McBSP port, as an array in case the
17 - interrupt-names: Array of strings associated with the interrupt numbers
|
| /Documentation/networking/ |
| D | fib_trie.rst | 15 An internal node, holding an array of child (leaf or tnode) pointers,
22 child array - the "child index". See Level Compression.
26 the child array. See Path Compression.
29 Any given tnode is linked to from the child array of its parent, using
43 contain an arbitrarily large array of links to several children.
44 Conversely, a tnode with a mostly empty child array (see empty_children)
49 the number of positions in the child array of a given tnode that are
85 Analyzes a tnode and optimizes the child array size by either inflating
91 Doubles the size of the child array within a tnode. Used by resize().
94 Halves the size of the child array within a tnode - the inverse of
[all …]
|
| /Documentation/devicetree/bindings/powerpc/opal/ |
| D | power-mgt.txt | 28 properties are exposed as arrays. Each entry in the property array
30 the array index of that entry.
38 Array of strings containing the names of the idle states.
41 Array of unsigned 32-bit values containing the values of the
61 Array of unsigned 32-bit values containing the values of the
66 Array of unsigned 32-bit values containing the values of the
74 Array of unsigned 64-bit values containing the values for the
79 Array of unsigned 64-bit values containing the masks
107 Array of unsigned 64-bit values containing the pmicr values
115 Array of unsigned 64-bit values containing the mask indicating
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | common.yaml | 38 Array of distinct brightness levels. The levels must be in the range
43 in the array represents a full 100% brightness (brightest).
44 If this array is not provided, the driver default mapping is used.
45 $ref: /schemas/types.yaml#/definitions/uint32-array
49 The default brightness level (index into the array defined by the
|
| /Documentation/devicetree/bindings/net/ |
| D | intel,ixp4xx-hss.yaml | 27 $ref: /schemas/types.yaml#/definitions/phandle-array
36 $ref: /schemas/types.yaml#/definitions/phandle-array
44 $ref: /schemas/types.yaml#/definitions/phandle-array
52 $ref: /schemas/types.yaml#/definitions/phandle-array
60 $ref: /schemas/types.yaml#/definitions/phandle-array
69 $ref: /schemas/types.yaml#/definitions/phandle-array
79 $ref: /schemas/types.yaml#/definitions/phandle-array
|
| /Documentation/netlink/ |
| D | genetlink.yaml | 43 type: array
67 description: For enum or flags array of values.
68 type: array
88 type: array
116 type: array
127 string, nest, indexed-array, nest-type-value ]
136 type: array
237 type: array
259 type: array
264 type: array
[all …]
|
| /Documentation/staging/ |
| D | speculation.rst | 24 int load_array(int *array, unsigned int index)
29 return array[index];
39 LDR <returnval>, [<array>, <index>]
43 speculatively loads array[index], even if index >= MAX_ARRAY_ELEMS. This
84 int load_array(int *array, unsigned int index)
90 return array[index];
|
| /Documentation/userspace-api/netlink/ |
| D | genetlink-legacy.rst | 33 define array types reusing attribute type to carry information.
35 For reference the ``multi-attr`` array may look like this::
37 [ARRAY-ATTR]
42 [ARRAY-ATTR]
47 where ``ARRAY-ATTR`` is the array entry type.
49 indexed-array
52 ``indexed-array`` wraps the entire array in an extra attribute (hence
61 [ARRAY-ATTR]
73 [ARRAY-ATTR]
81 information about a single object (often used when array is dumped
|
12345678910>>...40