Home
last modified time | relevance | path

Searched full:contiguous (Results 1 – 25 of 987) sorted by relevance

12345678910>>...40

/linux-6.8/kernel/dma/
DKconfig157 bool "DMA Contiguous Memory Allocator"
160 This enables the Contiguous Memory Allocator which allows drivers
161 to allocate big physically-contiguous blocks of memory for use with
167 For more information see <kernel/dma/contiguous.c>.
173 bool "Enable separate DMA Contiguous Memory Area for NUMA Node"
183 comment "Default contiguous memory area size:"
191 Defines the size (in MiB) of the default memory area for Contiguous
202 Defines the size of the default memory area for Contiguous Memory
226 int "Maximum PAGE_SIZE order of alignment for contiguous buffers"
234 specify the maximum PAGE_SIZE order for contiguous buffers. Larger
Dcontiguous.c3 * Contiguous Memory Allocator for DMA mapping framework
9 * Contiguous Memory Allocator
11 * The Contiguous Memory Allocator (CMA) makes it possible to
12 * allocate big contiguous chunks of memory after the system has
18 * IO map support and require contiguous blocks of memory to
210 * dma_contiguous_reserve() - reserve area(s) for contiguous memory handling
264 * dma_contiguous_reserve_area() - reserve custom contiguous area
277 * If @fixed is true, reserve contiguous area at exactly @base. If false,
291 /* Architecture specific contiguous memory fixup. */ in dma_contiguous_reserve_area()
299 * dma_alloc_from_contiguous() - allocate pages from contiguous area
[all …]
/linux-6.8/Documentation/arch/arm64/
Dhugetlbpage.rst23 2) Using the Contiguous bit
26 The architecture provides a contiguous bit in the translation table entries
28 contiguous set of entries that can be cached in a single TLB entry.
30 The contiguous bit is used in Linux to increase the mapping size at the pmd and
31 pte (last) level. The number of supported contiguous entries varies by page size
/linux-6.8/Documentation/networking/
Dsmc-sysctl.rst29 Default: 0 (physically contiguous sndbufs and RMBs)
33 - 0 - Use physically contiguous buffers
34 - 1 - Use virtually contiguous buffers
35 - 2 - Mixed use of the two types. Try physically contiguous buffers first.
36 If not available, use virtually contiguous buffers then.
/linux-6.8/drivers/gpu/drm/xe/
Dxe_bo_doc.h32 * vmap (XE can access the memory via xe_map layer) and have contiguous physical
35 * More details of why kernel BOs are pinned and contiguous below.
144 * makes this rather easy but the caveat is the memory must be contiguous. Again
145 * for simplity, we enforce that all kernel (pinned) BOs are contiguous and
164 * Do not require kernel BOs to be contiguous in physical memory / restored to
167 * tables. All of that memory is allocated 1 page at time so the contiguous
169 * kernel BOs are not contiguous too.
/linux-6.8/Documentation/admin-guide/
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-6.8/arch/nios2/
DKconfig49 int "Order of maximal physically contiguous allocations"
53 contiguous allocations. The limit is called MAX_PAGE_ORDER and it
55 allocated as a single contiguous block. This option allows
57 large blocks of physically contiguous memory is required.
/linux-6.8/drivers/gpu/drm/
Ddrm_gem_dma_helper.c30 * presented to the device as a contiguous chunk of memory. This is useful
37 * are contiguous in the IOVA space so appear contiguous to devices using
41 * objects that are physically contiguous in memory.
122 * The allocated memory will occupy a contiguous chunk of bus address space.
125 * memory will be physically contiguous. For devices that access through an
126 * IOMMU, then the allocated memory is not expected to be physically contiguous
127 * because having contiguous IOVAs is sufficient to meet a devices DMA
183 * The allocated memory will occupy a contiguous chunk of bus address space.
452 * another driver. Imported buffers must be physically contiguous in memory
468 /* check if the entries in the sg_table are contiguous */ in drm_gem_dma_prime_import_sg_table()
Ddrm_fb_dma_helper.c25 * Provides helper functions for creating a DMA-contiguous framebuffer.
27 * Depending on the platform, the buffers may be physically non-contiguous and
29 * physically-contiguous memory (using, for instance, CMA or a pool of memory
34 * callback function to create a DMA-contiguous framebuffer.
/linux-6.8/mm/
Dcma.c3 * Contiguous Memory Allocator
163 * cma_init_reserved_mem() - create custom contiguous area from reserved memory
172 * This function creates custom contiguous area from already reserved memory.
220 * cma_declare_contiguous_nid() - reserve custom contiguous area
236 * If @fixed is true, reserve contiguous area at exactly @base. If false,
420 * cma_alloc() - allocate pages from contiguous area
421 * @cma: Contiguous memory region for which the allocation is performed.
426 * This function allocates part of contiguous memory on specific
427 * contiguous memory area.
552 * @cma: Contiguous memory region for which the allocation is performed.
[all …]
Dpercpu-km.c8 * Chunks are allocated as a contiguous kernel memory using gfp
24 * PAGE_SIZE. Because each chunk is allocated as a contiguous
30 #error "contiguous percpu allocation is incompatible with paged first chunk"
Dutil.c125 * result is physically contiguous. Use kfree() to free.
146 * result may be not physically contiguous. Use kvfree() to free.
191 * contiguous, to be freed by kfree().
217 * physically contiguous. Use kvfree() to free.
580 * kvmalloc_node - attempt to allocate physically contiguous memory, but upon
581 * failure, fall back to non-contiguous (vmalloc) allocation.
601 * We want to attempt a large physically contiguous block first because in kvmalloc_node()
701 * __vmalloc_array - allocate memory for a virtually contiguous array.
717 * vmalloc_array - allocate memory for a virtually contiguous array.
728 * __vcalloc - allocate and zero memory for a virtually contiguous array.
[all …]
/linux-6.8/drivers/gpu/drm/exynos/
Dexynos_drm_gem.c36 * if EXYNOS_BO_CONTIG, fully physically contiguous memory in exynos_drm_alloc_buf()
37 * region will be allocated else physically contiguous in exynos_drm_alloc_buf()
210 * contiguous anyway, so drop EXYNOS_BO_NONCONTIG flag in exynos_drm_gem_create()
213 …DRM_WARN("Non-contiguous allocation is not supported without IOMMU, falling back to contiguous buf… in exynos_drm_gem_create()
435 /* check if the entries in the sg_table are contiguous */ in exynos_drm_gem_prime_import_sg_table()
446 * Buffer has been mapped as contiguous into DMA address space, in exynos_drm_gem_prime_import_sg_table()
/linux-6.8/Documentation/mm/
Dmemory-model.rst9 spans a contiguous range up to the maximal address. It could be,
11 for the CPU. Then there could be several contiguous ranges at
35 non-NUMA systems with contiguous, or mostly contiguous, physical
114 page *vmemmap` pointer that points to a virtually contiguous array of
/linux-6.8/arch/sh/mm/
DKconfig22 int "Order of maximal physically contiguous allocations"
29 contiguous allocations. The limit is called MAX_PAGE:_ORDER and it
31 allocated as a single contiguous block. This option allows
33 large blocks of physically contiguous memory is required.
/linux-6.8/Documentation/admin-guide/mm/
Dnommu-mmap.rst24 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-6.8/arch/arm64/mm/
Dhugetlbpage.c174 * Changing some bits of contiguous entries requires us to follow a
175 * Break-Before-Make approach, breaking the whole contiguous set
177 * "Misprogramming of the Contiguous bit", page D4-1762.
221 * Changing some bits of contiguous entries requires us to follow a
222 * Break-Before-Make approach, breaking the whole contiguous set
224 * "Misprogramming of the Contiguous bit", page D4-1762.
425 * For a contiguous huge pte range we need to check whether or not write
427 * all the contiguous ptes we need to check whether or not there is a
/linux-6.8/drivers/iio/common/cros_ec_sensors/
DKconfig17 tristate "ChromeOS EC Contiguous Sensors"
20 Module to handle 3d contiguous sensors like
/linux-6.8/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
235 - If you want to transfer a single contiguous memory buffer,
252 - These transfers can transfer data from a non-contiguous buffer
253 to a non-contiguous buffer, opposed to DMA_SLAVE that can
254 transfer data from a non-contiguous data set to a continuous
645 - Chunk: A contiguous collection of bursts
647 - Transfer: A collection of chunks (be it contiguous or not)
/linux-6.8/arch/m68k/
DKconfig.cpu392 Ignore all but the first contiguous chunk of physical memory for VM
400 int "Order of maximal physically contiguous allocations" if ADVANCED
405 contiguous allocations. The limit is called MAX_PAGE_ORDER and it
407 allocated as a single contiguous block. This option allows
409 large blocks of physically contiguous memory is required.
/linux-6.8/sound/pci/ctxfi/
Dctresource.c37 break; /* found sufficient contiguous resources */ in get_resource()
41 /* Can not find sufficient contiguous resources */ in get_resource()
45 /* Mark the contiguous bits in resource bit-map as used */ in get_resource()
62 /* Mark the contiguous bits in resource bit-map as used */ in put_resource()
/linux-6.8/Documentation/devicetree/bindings/gpio/
Drenesas,em-gio.yaml18 - description: First set of contiguous registers
19 - description: Second set of contiguous registers
/linux-6.8/Documentation/dev-tools/
Dkmsan.rst386 This means that in general for two contiguous memory pages their shadow/origin
387 pages may not be contiguous. Consequently, if a memory access crosses the
391 In practice, contiguous memory pages returned by the same ``alloc_pages()``
392 call will have contiguous metadata, whereas if these pages belong to two
399 pages with non-contiguous metadata, it returns pointers to fake shadow/origin regions::
415 When an array of pages is mapped into a contiguous virtual memory space, their
416 shadow and origin pages are similarly mapped into contiguous regions.
/linux-6.8/fs/jfs/
Djfs_dmap.c441 * nblocks - number of contiguous blocks in the range.
690 * FUNCTION: attempt to allocate a specified number of contiguous free
716 * nblocks - number of contiguous blocks in the range.
718 * of the newly allocated contiguous range.
913 * allocate a new set of contiguous blocks large enough
920 * nblocks - number of contiguous blocks within the current
925 * was extended in place or to a newly allocated contiguous
952 * a range of contiguous blocks large enough to cover the in dbReAlloc()
974 * nblocks - number of contiguous blocks within the current
1073 * nblocks - number of contiguous free blocks of the range.
[all …]
/linux-6.8/arch/x86/kernel/cpu/resctrl/
Dctrlmondata.c90 * On Intel CPUs, non-contiguous 1s value support is indicated by CPUID:
91 * - CPUID.0x10.1:ECX[3]: L3 non-contiguous 1s value supported if 1
92 * - CPUID.0x10.2:ECX[3]: L2 non-contiguous 1s value supported if 1
94 * Haswell does not support a non-contiguous 1s value and additionally
96 * AMD allows non-contiguous bitmasks.
118 /* Are non-contiguous bitmasks allowed? */ in cbm_validate()

12345678910>>...40