Home
last modified time | relevance | path

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

12345678910>>...43

/linux-6.14.4/kernel/dma/
DKconfig161 bool "DMA Contiguous Memory Allocator"
164 This enables the Contiguous Memory Allocator which allows drivers
165 to allocate big physically-contiguous blocks of memory for use with
171 For more information see <kernel/dma/contiguous.c>.
177 bool "Enable separate DMA Contiguous Memory Area for NUMA Node"
187 comment "Default contiguous memory area size:"
195 Defines the size (in MiB) of the default memory area for Contiguous
206 Defines the size of the default memory area for Contiguous Memory
230 int "Maximum PAGE_SIZE order of alignment for contiguous buffers"
238 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
204 * dma_contiguous_reserve() - reserve area(s) for contiguous memory handling
258 * dma_contiguous_reserve_area() - reserve custom contiguous area
271 * If @fixed is true, reserve contiguous area at exactly @base. If false,
285 /* Architecture specific contiguous memory fixup. */ in dma_contiguous_reserve_area()
293 * dma_alloc_from_contiguous() - allocate pages from contiguous area
[all …]
/linux-6.14.4/tools/testing/selftests/resctrl/
Dcat_test.c248 /* Get the largest contiguous exclusive portion of the cache */ in cat_run_test()
293 /* AMD always supports non-contiguous CBM. */ in arch_supports_noncont_cat()
299 /* Intel support for non-contiguous CBM needs to be discovered. */ in arch_supports_noncont_cat()
327 ksft_print_msg("Hardware and kernel differ on non-contiguous CBM support!\n"); in noncont_cat_run_test()
346 /* Contiguous mask write check. */ in noncont_cat_run_test()
350 ksft_print_msg("Write of contiguous CBM failed\n"); in noncont_cat_run_test()
355 * Non-contiguous mask write check. CBM has a 0xf hole approximately in the middle. in noncont_cat_run_test()
362 ksft_print_msg("Non-contiguous CBMs supported but write of non-contiguous CBM failed\n"); in noncont_cat_run_test()
364 …ksft_print_msg("Non-contiguous CBMs not supported and write of non-contiguous CBM failed as expect… in noncont_cat_run_test()
366 ksft_print_msg("Non-contiguous CBMs not supported but write of non-contiguous CBM succeeded\n"); in noncont_cat_run_test()
/linux-6.14.4/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.14.4/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.14.4/arch/arm64/kernel/pi/
Dmap_range.c15 * map_range - Map a contiguous range of physical pages into virtual memory
25 * @may_use_cont: Whether the use of the contiguous attribute is allowed
68 * Start a contiguous range if start and pa are in map_range()
75 * Clear the contiguous attribute if the remaining in map_range()
76 * range does not cover a contiguous block in map_range()
/linux-6.14.4/tools/perf/pmu-events/arch/arm64/fujitsu/monaka/
Dsve.json188 …ecuted operations that prefetch memory due to an SVE predicated single contiguous element prefetch…
192 … reads from memory with a non-temporal hint due to an SVE non-temporal contiguous element load ins…
196 …t writes to memory with a non-temporal hint due to an SVE non-temporal contiguous element store in…
200 …ons that read from memory due to SVE and Advanced SIMD multiple vector contiguous structure load i…
204 …ions that write to memory due to SVE and Advanced SIMD multiple vector contiguous structure store …
208 …chitecturally executed operations that read from memory due to SVE non-contiguous gather-load inst…
212 …rchitecturally executed operations that write to memory due to SVE non-contiguous scatter-store in…
216 …rchitecturally executed operations that prefetch memory due to SVE non-contiguous gather-prefetch …
/linux-6.14.4/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.14.4/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.14.4/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.c26 * Provides helper functions for creating a DMA-contiguous framebuffer.
28 * Depending on the platform, the buffers may be physically non-contiguous and
30 * physically-contiguous memory (using, for instance, CMA or a pool of memory
35 * callback function to create a DMA-contiguous framebuffer.
/linux-6.14.4/arch/nios2/
DKconfig51 int "Order of maximal physically contiguous allocations"
55 contiguous allocations. The limit is called MAX_PAGE_ORDER and it
57 allocated as a single contiguous block. This option allows
59 large blocks of physically contiguous memory is required.
/linux-6.14.4/mm/
Dcma.c3 * Contiguous Memory Allocator
157 * cma_init_reserved_mem() - create custom contiguous area from reserved memory
166 * This function creates custom contiguous area from already reserved memory.
219 * cma_declare_contiguous_nid() - reserve custom contiguous area
235 * If @fixed is true, reserve contiguous area at exactly @base. If false,
514 * cma_alloc() - allocate pages from contiguous area
515 * @cma: Contiguous memory region for which the allocation is performed.
520 * This function allocates part of contiguous memory on specific
521 * contiguous memory area.
562 * @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"
/linux-6.14.4/arch/sh/mm/
DKconfig34 int "Order of maximal physically contiguous allocations"
41 contiguous allocations. The limit is called MAX_PAGE:_ORDER and it
43 allocated as a single contiguous block. This option allows
45 large blocks of physically contiguous memory is required.
/linux-6.14.4/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.14.4/arch/arm64/mm/
Dcontpte.c84 * with contiguous PFNs and matching prots. We ignore the state of the in __contpte_try_fold()
85 * access and dirty bits for the purpose of deciding if its a contiguous in __contpte_try_fold()
144 * We have already checked that the ptes are contiguous in in __contpte_try_unfold()
160 * contiguous range cannot be unfolded or otherwise modified under our in contpte_ptep_get()
190 * access and dirty bits from across all ptes in the contiguous block, in contpte_ptep_get_lockless()
192 * contiguous range may be unfolded/modified/refolded under our feet. in contpte_ptep_get_lockless()
195 * pfns are contiguous and that all pgprots are the same (ignoring in contpte_ptep_get_lockless()
402 * Gather the access/dirty bits for the contiguous range. If nothing has in contpte_ptep_set_access_flags()
Dhugetlbpage.c146 * Changing some bits of contiguous entries requires us to follow a
147 * Break-Before-Make approach, breaking the whole contiguous set
149 * "Misprogramming of the Contiguous bit", page D4-1762.
192 * Changing some bits of contiguous entries requires us to follow a
193 * Break-Before-Make approach, breaking the whole contiguous set
195 * "Misprogramming of the Contiguous bit", page D4-1762.
405 * For a contiguous huge pte range we need to check whether or not write
407 * all the contiguous ptes we need to check whether or not there is a
/linux-6.14.4/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.14.4/rust/kernel/alloc/
Dallocator.rs20 /// The contiguous kernel allocator.
22 /// `Kmalloc` is typically used for physically contiguous allocations up to page size, but also
28 /// The virtually contiguous kernel allocator.
30 /// `Vmalloc` allocates pages from the page level allocator and maps them into the contiguous kernel
32 /// allocator is not physically contiguous.
/linux-6.14.4/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.14.4/drivers/iio/common/cros_ec_sensors/
DKconfig17 tristate "ChromeOS EC Contiguous Sensors"
20 Module to handle 3d contiguous sensors like
/linux-6.14.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
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
655 - Chunk: A contiguous collection of bursts
657 - Transfer: A collection of chunks (be it contiguous or not)
/linux-6.14.4/Documentation/core-api/
Dswiotlb.rst64 buffer memory is physically contiguous. The expectation is that the DMA layer
90 allocations must be physically contiguous, the entire default memory pool is
91 allocated as a single contiguous block.
147 the life of the system. Each pool must be a contiguous range of physical
154 current definitions. IO_TLB_SEGSIZE contiguous slots (128 slots) constitute
156 occupies one or more contiguous slots. A slot is never shared by multiple
211 must be physically contiguous, so the size is limited to MAX_PAGE_ORDER pages
285 in struct io_tlb_slot records how many contiguous available slots exist starting
/linux-6.14.4/arch/m68k/
DKconfig.cpu404 Ignore all but the first contiguous chunk of physical memory for VM
412 int "Order of maximal physically contiguous allocations" if ADVANCED
417 contiguous allocations. The limit is called MAX_PAGE_ORDER and it
419 allocated as a single contiguous block. This option allows
421 large blocks of physically contiguous memory is required.

12345678910>>...43