| /linux-5.19.10/drivers/acpi/acpica/ |
| D | uttrack.c | 32 *allocation);
94 struct acpi_debug_mem_block *allocation; in acpi_ut_allocate_and_track() local
105 allocation = in acpi_ut_allocate_and_track()
107 if (!allocation) { in acpi_ut_allocate_and_track()
118 acpi_ut_track_allocation(allocation, size, ACPI_MEM_MALLOC, in acpi_ut_allocate_and_track()
121 acpi_os_free(allocation); in acpi_ut_allocate_and_track()
135 return ((void *)&allocation->user_space); in acpi_ut_allocate_and_track()
157 struct acpi_debug_mem_block *allocation; in acpi_ut_allocate_zeroed_and_track() local
168 allocation = in acpi_ut_allocate_zeroed_and_track()
171 if (!allocation) { in acpi_ut_allocate_zeroed_and_track()
[all …]
|
| D | utalloc.c | 33 void *allocation; in acpi_os_allocate_zeroed() local
37 allocation = acpi_os_allocate(size); in acpi_os_allocate_zeroed()
38 if (allocation) { in acpi_os_allocate_zeroed()
42 memset(allocation, 0, size); in acpi_os_allocate_zeroed()
45 return (allocation); in acpi_os_allocate_zeroed()
|
| /linux-5.19.10/tools/testing/selftests/resctrl/ |
| D | mba_test.c | 27 static int runs_per_allocation, allocation = 100; in mba_setup() local
43 if (allocation < ALLOCATION_MIN || allocation > ALLOCATION_MAX) in mba_setup()
46 sprintf(allocation_str, "%d", allocation); in mba_setup()
49 allocation -= ALLOCATION_STEP; in mba_setup()
56 int allocation, runs; in show_mba_info() local
61 for (allocation = 0; allocation < ALLOCATION_MAX / ALLOCATION_STEP; in show_mba_info()
62 allocation++) { in show_mba_info()
72 for (runs = NUM_OF_RUNS * allocation + 1; in show_mba_info()
73 runs < NUM_OF_RUNS * allocation + NUM_OF_RUNS ; runs++) { in show_mba_info()
87 ALLOCATION_MAX - ALLOCATION_STEP * allocation); in show_mba_info()
|
| /linux-5.19.10/mm/ |
| D | dmapool.c | 48 size_t allocation; member
95 pages * (pool->allocation / pool->size), in pools_show()
134 size_t allocation; in dma_pool_create() local
148 allocation = max_t(size_t, size, PAGE_SIZE); in dma_pool_create()
151 boundary = allocation; in dma_pool_create()
167 retval->allocation = allocation; in dma_pool_create()
216 } while (offset < pool->allocation); in pool_initialise_page()
226 page->vaddr = dma_alloc_coherent(pool->dev, pool->allocation, in pool_alloc_page()
230 memset(page->vaddr, POOL_POISON_FREED, pool->allocation); in pool_alloc_page()
252 memset(page->vaddr, POOL_POISON_FREED, pool->allocation); in pool_free_page()
[all …]
|
| /linux-5.19.10/Documentation/core-api/ |
| D | memory-allocation.rst | 7 Linux provides a variety of APIs for memory allocation. You can
14 Most of the memory allocation APIs use GFP flags to express how that
16 pages", the underlying memory allocation function.
18 Diversity of the allocation APIs combined with the numerous GFP flags
26 Of course there are cases when other allocation APIs and different GFP
45 * If the allocation is performed from an atomic context, e.g interrupt
48 ``GFP_NOWAIT`` allocation is likely to fail. Allocations which
51 will be stressed unless allocation succeeds, you may use ``GFP_ATOMIC``.
66 example may be a hardware allocation that maps data directly into
93 * ``GFP_KERNEL & ~__GFP_RECLAIM`` - optimistic allocation without _any_
[all …]
|
| D | genalloc.rst | 4 There are a number of memory-allocation subsystems in the kernel, each
32 which NUMA node should be used for the allocation of the housekeeping
87 how the allocation functions choose which specific piece of memory to
107 - gen_pool_first_fit_align forces the allocation to have a specific
110 - gen_pool_first_fit_order_align aligns the allocation to the order of the
111 size. A 60-byte allocation will thus be 64-byte aligned, for example.
117 If the indicated memory is not available the allocation fails.
|
| /linux-5.19.10/include/linux/ |
| D | dmapool.h | 22 size_t size, size_t align, size_t allocation);
34 size_t size, size_t align, size_t allocation);
39 struct device *dev, size_t size, size_t align, size_t allocation) in dma_pool_create() argument
47 struct device *dev, size_t size, size_t align, size_t allocation) in dmam_pool_create() argument
|
| /linux-5.19.10/Documentation/trace/ |
| D | events-kmem.rst | 5 The kmem tracing system captures events related to object and page allocation
8 - Slab allocation of small objects of unknown type (kmalloc)
9 - Slab allocation of small objects of known type
10 - Page allocation
17 1. Slab allocation of small objects of unknown type
27 internal fragmented as a result of the allocation pattern. By correlating
29 the allocation sites were.
32 2. Slab allocation of small objects of known type
45 3. Page allocation
54 These four events deal with page allocation and freeing. mm_page_alloc is
[all …]
|
| /linux-5.19.10/Documentation/vm/ |
| D | page_frags.rst | 13 simple allocation framework for page fragments. This is used by the
19 cache is needed. This provides a central point for the fragment allocation
22 which can be expensive at allocation time. However due to the nature of
25 to be disabled when executing the fragment allocation.
28 allocation. The netdev_alloc_cache is used by callers making use of the
43 avoid calling get_page per allocation.
|
| D | split_page_table_lock.rst | 25 to taken lock or NULL if allocation failed;
59 must be called on PTE table allocation / freeing.
62 allocation: slab uses page->slab_cache for its pages.
69 allocation and pgtable_pmd_page_dtor() on freeing.
72 pmd_free_tlb(), but make sure you cover all PMD table allocation / freeing
|
| D | balance.rst | 14 be that the caller is willing to fail the allocation without incurring the
16 allocation requests that have order-0 fallback options. In such cases,
19 __GFP_IO allocation requests are made to prevent file system deadlocks.
21 In the absence of non sleepable allocation requests, it seems detrimental
48 with a slight change in the allocation routine, it is possible to reduce
76 probably because all allocation requests are coming from intr context
90 watermark[WMARK_HIGH]. When low_on_memory is set, page allocation requests will
|
| D | page_owner.rst | 12 When allocation happens, information about allocation such as call stack
17 Although we already have tracepoint for tracing page allocation/free,
35 the page allocator hotpath and if not enabled, then allocation is done
37 not affect to allocation performance, especially if the static keys jump
116 -a Sort by memory allocation time.
182 st stacktrace stack trace of the page allocation
195 st stacktrace stack trace of the page allocation
|
| D | numa.rst | 77 selected zone/node cannot satisfy the allocation request. This situation,
89 By default, Linux will attempt to satisfy memory allocation requests from the
92 for the node where the request originates. This is called "local allocation."
97 Local allocation will tend to keep subsequent access to the allocated memory
112 allocation behavior using Linux NUMA memory policy. [see
129 Some kernel allocations do not want or cannot tolerate this allocation fallback
134 A typical model for making such an allocation is to obtain the node id of the
137 the node id returned. When such an allocation fails, the requesting subsystem
140 itself on allocation failure. The kernel profiling subsystem is an example of
|
| /linux-5.19.10/Documentation/filesystems/ext4/ |
| D | bigalloc.rst | 15 use clustered allocation, so that each bit in the ext4 block allocation
19 This means that each bit in the block allocation bitmap now addresses
20 256 4k blocks. This shrinks the total size of the block allocation
29 128MiB); however, the minimum allocation unit becomes a cluster, not a
|
| /linux-5.19.10/tools/testing/memblock/ |
| D | README | 17 allocation functionalities of memblock. The main data structure of the boot time
47 allocation functions. Tests for each group are defined in dedicated files, as it
71 Some allocation functions clear the memory in the process, so it is required for
74 points to a block of memory allocated via malloc. For each group of allocation
76 at the end of the test run. The structure of a test runner checking allocation
84 (...allocation checks...)
|
| /linux-5.19.10/Documentation/admin-guide/mm/ |
| D | numa_memory_policy.rst | 40 use "local allocation" described below. However, during boot
84 A VMA policy will govern the allocation of pages that back
140 support allocation at fault time--a.k.a lazy allocation--so hugetlbfs
142 Although hugetlbfs segments now support lazy allocation, their support
199 closest to the node where the allocation takes place.
202 This mode specifies that the allocation should be attempted
204 allocation fails, the kernel will search other nodes, in order
211 and the policy is interpreted as local allocation. "Local"
212 allocation policy can be viewed as a Preferred policy that
213 starts at the node containing the cpu where the allocation
[all …]
|
| /linux-5.19.10/Documentation/admin-guide/ |
| D | numastat.rst | 12 the preferred node and numa_miss on the node where allocation succeeded.
17 incremented on allocation from a node by CPU on the same node. other_node is
18 similar to numa_miss and is incremented on the node where allocation succeeds
53 preferred node. As a result, such allocation will not increase the numa_foreign
|
| /linux-5.19.10/drivers/soundwire/ |
| D | Makefile | 11 soundwire-generic-allocation-objs := generic_bandwidth_allocation.o
12 obj-$(CONFIG_SOUNDWIRE_GENERIC_ALLOCATION) += soundwire-generic-allocation.o
|
| /linux-5.19.10/drivers/staging/gdm724x/ |
| D | TODO | 10 - Review use of atomic allocation for tx structs
12 - fix up static tty port allocation to be dynamic
|
| /linux-5.19.10/arch/powerpc/platforms/powernv/ |
| D | Kconfig | 30 bool "Enable runtime allocation of RAM for tracing"
33 Enabling this option allows for runtime allocation of memory (RAM)
|
| /linux-5.19.10/Documentation/translations/zh_CN/core-api/ |
| D | memory-allocation.rst | 3 :Original: Documentation/core-api/memory-allocation.rst
13 .. _cn_core-api_memory-allocation:
|
| /linux-5.19.10/Documentation/arm64/ |
| D | memory-tagging-extension.rst | 19 allocation tag for each 16-byte granule in the physical address space.
23 the logical tag against the allocation tag and potentially raise an
36 To access the allocation tags, a user process must enable the Tagged
40 ``PROT_MTE`` - Pages allow access to the MTE allocation tags.
42 The allocation tag is set to 0 when such pages are first mapped in the
44 supported and the allocation tags can be shared between processes.
55 ``MADV_FREE`` may have the allocation tags cleared (set to 0) at any
62 the logical and allocation tags occurs on access, there are three
230 The allocation tags for user memory mapped with ``PROT_MTE`` are dumped
303 * Set the allocation tag on the destination address.
[all …]
|
| /linux-5.19.10/scripts/coccinelle/null/ |
| D | eno.cocci | 2 /// The various basic memory allocation functions don't return ERR_PTR
48 msg = "ERROR: allocation function on line %s returns NULL not ERR_PTR on failure" % (p1[0].line)
|
| /linux-5.19.10/Documentation/devicetree/bindings/dma/ti/ |
| D | k3-pktdma.yaml | 62 Array of PKTDMA split tx channel resource subtypes for resource allocation
73 Array of PKTDMA split tx flow resource subtypes for resource allocation
84 Array of PKTDMA split rx channel resource subtypes for resource allocation
95 Array of PKTDMA split rx flow resource subtypes for resource allocation
|
| /linux-5.19.10/fs/dlm/ |
| D | memory.c | 141 struct dlm_msg *dlm_allocate_msg(gfp_t allocation) in dlm_allocate_msg() argument
143 return kmem_cache_alloc(msg_cache, allocation); in dlm_allocate_msg()
|