Searched full:array (Results 1 – 25 of 702) sorted by relevance
12345678910>>...29
| /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/RCU/ |
| D | arrayRCU.rst | 16 array that is separately indexed. It might be tempting to consider use
17 of RCU to instead protect the index into an array, however, this use
34 Hash tables are often implemented as an array, where each array entry
37 to other array-of-list situations, such as radix trees.
45 located in each array element, and where the array is never resized,
61 function formerly used by the System V IPC code. The array is used
70 the new array, and invokes ipc_rcu_putref() to free up the old array.
102 * contents of the new array are visible before the new
103 * array becomes visible.
111 The ipc_rcu_putref() function decrements the array's reference count
[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 …]
|
| D | xarray.rst | 12 The XArray is an abstract data type which behaves like a very large array
14 resizable array. Unlike a hash, it allows you to sensibly go to the
16 resizable array, there is no need to copy data or change MMU mappings in
17 order to grow the array. It is more memory-efficient, parallelisable
84 You can copy entries out of the XArray into a plain array by calling
107 If all entries in the array are ``NULL``, the xa_empty() function
118 Each entry in the array has three bits associated with it called marks.
148 in the XArray. If you need to modify the array from interrupt context,
240 prevent stores from removing the object from the array between looking
246 the array. It is safe to read the XArray from interrupt or softirq
[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/devicetree/bindings/usb/ |
| 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/devicetree/bindings/soundwire/ |
| D | qcom,sdw.txt | 18 Value type: <prop-encoded-array>
24 Value type: <prop-encoded-array>
34 Value type: <prop-encoded-array>
54 Value type: <prop-encoded-array>
61 Value type: <prop-encoded-array>
68 Value type: <prop-encoded-array>
76 Value type: <prop-encoded-array>
82 Value type: <prop-encoded-array>
91 Value type: <prop-encoded-array>
99 Value type: <prop-encoded-array>
[all …]
|
| /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 …]
|
| /Documentation/vm/ |
| D | memory-model.rst | 44 In the FLATMEM memory model, there is a global `mem_map` array that
46 have entries in the `mem_map` array. The `struct page` objects
49 To allocate the `mem_map` array, architecture specific setup code should
50 call :c:func:`free_area_init` function. Yet, the mappings array is not
54 An architecture may free parts of the `mem_map` array that do not cover the
61 `mem_map` array.
73 things, `pg_data_t` holds the `node_mem_map` array that maps
84 `node_mem_map` array. When DISCONTIGMEM is enabled, a portion of the
99 appropriate `node_mem_map` array to access the `struct page` and
115 array of struct pages. However, it is stored with some other magic
[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/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 | 41 MADERA_INMODE_xxx. If the array is shorter than the number
43 $ref: /schemas/types.yaml#/definitions/uint32-array
53 Mono bit for each output, maximum of six cells if the array
55 $ref: /schemas/types.yaml#/definitions/uint32-array
75 $ref: /schemas/types.yaml#/definitions/uint32-array
89 $ref: /schemas/types.yaml#/definitions/uint32-array
101 $ref: /schemas/types.yaml#/definitions/uint32-array
111 $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
|
| D | wlf,arizona.yaml | 35 $ref: /schemas/types.yaml#/definitions/uint32-array
51 $ref: /schemas/types.yaml#/definitions/uint32-array
66 $ref: /schemas/types.yaml#/definitions/uint32-array
83 $ref: /schemas/types.yaml#/definitions/uint32-array
94 $ref: /schemas/types.yaml#/definitions/uint32-array
103 $ref: /schemas/types.yaml#/definitions/uint32-array
112 $ref: /schemas/types.yaml#/definitions/uint32-array
|
| /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/nvmem/ |
| D | nvmem-consumer.yaml | 16 $ref: /schemas/types.yaml#/definitions/phandle-array
21 $ref: /schemas/types.yaml#/definitions/phandle-array
26 $ref: /schemas/types.yaml#/definitions/string-array
31 $ref: /schemas/types.yaml#/definitions/string-array
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | led-backlight.yaml | 25 $ref: /schemas/types.yaml#/definitions/phandle-array
29 Array of distinct brightness levels. The levels must be in the range
33 $ref: /schemas/types.yaml#/definitions/uint32-array
37 The default brightness level (index into the array defined by the
|
| /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/devicetree/bindings/input/ |
| D | qcom,pm8xxx-keypad.txt | 14 Value type: <prop-encoded-array>
19 Value type: <prop-encoded-array>
27 Value type: <prop-encoded-array>
64 of the matrix array.
70 the matrix array.
|
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | srio-rmu.txt | 20 Value type: <prop-encoded-array>
27 Value type: <prop-encoded-array>
51 Value type: <prop-encoded-array>
58 Value type: <prop_encoded-array>
81 Value type: <prop-encoded-array>
88 Value type: <prop_encoded-array>
111 Value type: <prop-encoded-array>
118 Value type: <prop_encoded-array>
|
| /Documentation/leds/ |
| D | leds-class-multicolor.rst | 11 controlled via the multi_intensity array file and the latter is controlled
17 array. These files are children under the LED parent node created by the
25 The multi_index file is an array that contains the string list of the colors as
26 they are defined in each multi_* array file.
28 The multi_intensity is an array that can be read or written to for the
29 individual color intensities. All elements within this array must be written in
|
| /Documentation/filesystems/ |
| D | fiemap.rst | 25 __u32 fm_extent_count; /* size of fm_extents array (in) */
27 struct fiemap_extent fm_extents[0]; /* array of mapped extents (out) */
47 fm_extent_count specifies the number of elements in the fm_extents[] array
49 fm_extents[] array is ignored (no extents will be returned), and the
67 Extent information is returned within the embedded fm_extents array
69 number of elements in the fiemap_extents[] array should be passed via
74 array will be returned and fm_mapped_extents will be equal to
75 fm_extent_count. In that case, the last extent in the array will not
199 unsigned int fi_extents_max; /* Size of fiemap_extent array */
200 struct fiemap_extent *fi_extents_start; /* Start of fiemap_extent array */
[all …]
|
12345678910>>...29