Home
last modified time | relevance | path

Searched refs:contiguous (Results 1 – 25 of 146) sorted by relevance

123456

/Linux-v5.4/Documentation/arm64/
Dhugetlbpage.rst24 The architecture provides a contiguous bit in the translation table entries
26 contiguous set of entries that can be cached in a single TLB entry.
28 The contiguous bit is used in Linux to increase the mapping size at the pmd and
29 pte (last) level. The number of supported contiguous entries varies by page size
/Linux-v5.4/kernel/dma/
DKconfig85 to allocate big physically-contiguous blocks of memory for use with
91 For more information see <include/linux/dma-contiguous.h>.
95 comment "Default contiguous memory area size:"
138 int "Maximum PAGE_SIZE order of alignment for contiguous buffers"
146 specify the maximum PAGE_SIZE order for contiguous buffers. Larger
DMakefile4 obj-$(CONFIG_DMA_CMA) += contiguous.o
/Linux-v5.4/Documentation/driver-api/
Ddell_rbu.rst32 image methods. In case of monolithic the driver allocates a contiguous chunk
35 would place each packet in contiguous physical memory. The driver also
57 copied to a single contiguous block of physical memory.
60 of contiguous memory and the BIOS image is scattered in these packets.
84 the file and spreads it across the physical memory in contiguous packet_sized
/Linux-v5.4/drivers/misc/habanalabs/
Dmemory.c62 bool contiguous; in alloc_device_memory() local
70 contiguous = args->flags & HL_MEM_CONTIGUOUS; in alloc_device_memory()
72 if (contiguous) { in alloc_device_memory()
94 phys_pg_pack->contiguous = contiguous; in alloc_device_memory()
102 if (phys_pg_pack->contiguous) { in alloc_device_memory()
146 if (!phys_pg_pack->contiguous) in alloc_device_memory()
155 if (contiguous) in alloc_device_memory()
273 if (phys_pg_pack->contiguous) { in free_phys_pg_pack()
/Linux-v5.4/arch/x86/include/asm/
DKbuild10 generic-y += dma-contiguous.h
/Linux-v5.4/Documentation/devicetree/bindings/reserved-memory/
Dreserved-memory.txt69 region for the default pool of the contiguous memory allocator.
83 This example defines 3 contiguous regions are defined for Linux kernel:
101 /* global autoconfigured region for contiguous allocations */
/Linux-v5.4/Documentation/features/io/dma-contiguous/
Darch-support.txt2 # Feature name: dma-contiguous
/Linux-v5.4/Documentation/media/uapi/v4l/
Dpixfmt-nv16m.rst19 non contiguous in memory.
28 two planes are non-contiguous in memory, i.e. the chroma plane does not
Dpixfmt-nv12m.rst22 non contiguous in memory.
31 two planes are non-contiguous in memory, i.e. the chroma plane do not
/Linux-v5.4/Documentation/media/kapi/
Dv4l2-videobuf.rst45 contiguous; buffers allocated with vmalloc(), in other words. These
47 useful in situations where DMA is not available but virtually-contiguous
50 - Buffers which are physically contiguous. Allocation of this kind of
76 <media/videobuf-dma-contig.h> /* Physically contiguous */
335 same is normally true of contiguous-DMA drivers as well; videobuf will
342 As of 2.6.31, contiguous-DMA drivers can work with a user-supplied buffer,
343 as long as that buffer is physically contiguous. Normal user-space
385 For contiguous DMA drivers, the function to use is:
391 The contiguous DMA API goes out of its way to hide the kernel-space address
/Linux-v5.4/arch/xtensa/boot/dts/
Dkc705.dts21 /* global autoconfigured region for contiguous allocations */
/Linux-v5.4/Documentation/
Dnommu-mmap.txt24 In the no-MMU case: VM regions backed by arbitrary contiguous runs of
52 appropriate bit of the file will be read into a contiguous bit of
83 sequence by providing a contiguous sequence of pages to map. In that
93 blockdev must be able to provide a contiguous run of pages without
95 all its memory as a contiguous array upfront.
252 filesystem providing the service will probably allocate a contiguous collection
269 should allocate sufficient contiguous memory to honour any supported mapping.
/Linux-v5.4/arch/c6x/
DKconfig89 The kernel memory allocator divides physically contiguous memory
93 blocks of physically contiguous memory, then you may need to
/Linux-v5.4/Documentation/driver-api/dmaengine/
Dprovider.rst47 that involve a single contiguous block of data. However, some of the
49 non-contiguous buffers to a contiguous buffer, which is called
216 - If you want to transfer a single contiguous memory buffer,
233 - These transfers can transfer data from a non-contiguous buffer
234 to a non-contiguous buffer, opposed to DMA_SLAVE that can
235 transfer data from a non-contiguous data set to a continuous
502 - Chunk: A contiguous collection of bursts
504 - Transfer: A collection of chunks (be it contiguous or not)
/Linux-v5.4/arch/s390/include/asm/
DKbuild10 generic-y += dma-contiguous.h
/Linux-v5.4/arch/mips/include/asm/
DKbuild9 generic-y += dma-contiguous.h
/Linux-v5.4/arch/arm64/include/asm/
DKbuild6 generic-y += dma-contiguous.h
/Linux-v5.4/Documentation/x86/x86_64/
Dfake-numa-for-cpusets.rst13 you can create fake NUMA nodes that represent contiguous chunks of memory and
43 Documentation/admin-guide/cgroup-v1/cpusets.rst, you can assign fake nodes (i.e. contiguous memory
/Linux-v5.4/Documentation/vm/
Dmemory-model.rst11 spans a contiguous range up to the maximal address. It could be,
13 for the CPU. Then there could be several contiguous ranges at
41 non-NUMA systems with contiguous, or mostly contiguous, physical
162 page *vmemmap` pointer that points to a virtually contiguous array of
/Linux-v5.4/drivers/iio/common/cros_ec_sensors/
DKconfig20 Module to handle 3d contiguous sensors like
/Linux-v5.4/Documentation/devicetree/bindings/arm/omap/
Ddmm.txt7 translation for initiators which need contiguous dma bus addresses.
/Linux-v5.4/arch/xtensa/include/asm/
DKbuild7 generic-y += dma-contiguous.h
/Linux-v5.4/arch/riscv/include/asm/
DKbuild10 generic-y += dma-contiguous.h
/Linux-v5.4/Documentation/driver-api/fpga/
Dfpga-mgr.rst14 contiguous buffer, or a firmware file. Because allocating contiguous kernel

123456