| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-driver-wacom | 75 1024 byte binary is split up into 16x 64 byte chunks. Each 64
|
| /linux/Documentation/admin-guide/ |
| H A D | dell_rbu.rst | 59 In case of packet mechanism the single memory can be broken in smaller chunks
|
| H A D | kernel-parameters.txt | 1414 nochunk: disable reading files in "chunks" in the EFI
|
| H A D | md.rst | 215 This is the size in bytes for ``chunks`` and is only relevant to
217 of the array is conceptually divided into chunks and consecutive
218 chunks are striped onto neighbouring devices.
|
| H A D | pstore-blk.rst | 81 There are multiple chunks for oops/panic front-end depending on the remaining
84 pstore/blk will log to oops/panic chunks one by one, and always overwrite the
116 Similar to oops front-end, there are multiple chunks for ftrace front-end
|
| H A D | ramoops.rst | 36 The memory area is divided into ``record_size`` chunks (also rounded down to
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H A D | dm-zoned.rst | 106 be exhausted (all used to map chunks or buffer sequential zones) and
107 unaligned writes to unbuffered chunks become impossible. To avoid this
|
| H A D | linear.rst | 38 # Split a device into 4M chunks and then join them together in reverse order.
|
| H A D | snapshot.rst | 15 In the first two cases, dm copies only the chunks of data that get
37 A snapshot of the <origin> block device is created. Changed chunks of
61 maps to entire chunks to will zero the corresponding exception(s) in
81 Creates a merging snapshot that takes control of the changed chunks
83 procedure, and merges these chunks back into the <origin>. Once merging
|
| H A D | striped.rst | 6 device across one or more underlying devices. Data is written in "chunks",
7 with consecutive chunks rotating among the underlying devices. This can
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | memory-hotplug.rst | 42 physical memory address space into chunks of the same size: memory sections. The
46 Memory sections are combined into chunks referred to as "memory blocks". The
|
| /linux/Documentation/arch/powerpc/ |
| H A D | cxl.rst | 421 chunks.
|
| /linux/Documentation/arch/sparc/oradax/ |
| H A D | dax-hv-api.txt | 383 …subsequent data chunks may not be detected, so guest software should be careful to use page size c…
|
| /linux/Documentation/arch/x86/ |
| H A D | boot.rst | 832 chunks of memory are occupied by kernel data.
|
| /linux/Documentation/arch/x86/x86_64/ |
| H A D | fake-numa-for-cpusets.rst | 13 you can create fake NUMA nodes that represent contiguous chunks of memory and
25 four equal chunks of 512M each that we can now use to assign to cpusets. As
|
| /linux/Documentation/block/ |
| H A D | data-integrity.rst | 121 space is limited, the block interface allows tagging bigger chunks by
|
| /linux/Documentation/core-api/ |
| H A D | assoc_array.rst | 342 The index key is read in chunks of machine word. Each chunk is subdivided into
|
| H A D | genalloc.rst | 120 the space available in the pool or iterating through chunks of memory.
|
| H A D | memory-allocation.rst | 8 allocate small chunks using `kmalloc` or `kmem_cache_alloc` families,
|
| H A D | padata.rst | 161 finished. padata splits the job into units called chunks, where a chunk is a
|
| /linux/Documentation/crypto/ |
| H A D | devel-algos.rst | 131 hardware needs to be fed separate chunks of the scatterlist which
237 implementation needs to be fed separate chunks of the scatterlist which
|
| /linux/Documentation/dev-tools/ |
| H A D | checkuapi.rst | 344 You can use the ``-b`` and ``-p`` options to examine different chunks of your
|
| /linux/Documentation/devicetree/bindings/iommu/ |
| H A D | samsung,sysmmu.yaml | 14 physical memory chunks visible as a contiguous region to DMA-capable peripheral
|
| /linux/Documentation/devicetree/bindings/serial/ |
| H A D | fsl-imx-uart.yaml | 99 First cell contains the size of DMA buffer chunks, second cell contains
100 the amount of chunks used for the device. Multiplying both numbers is
|
| /linux/Documentation/driver-api/dmaengine/ |
| H A D | provider.rst | 58 The latter are usually programmed using a collection of chunks to
137 your device is able to report which chunks have been transferred
165 - No matter what the overall size of the combined chunks for source and
647 - Transfer: A collection of chunks (be it contiguous or not)
|