| /linux/Documentation/trace/ |
| H A 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/Documentation/core-api/ |
| H A 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. Users of this flag need
52 will be stressed unless allocation succeeds, you may use ``GFP_ATOMIC``.
67 example may be a hardware allocation that maps data directly into
94 * ``GFP_KERNEL & ~__GFP_RECLAIM`` - optimistic allocation without _any_
[all …]
|
| H A 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.
|
| H A D | boot-time-mm.rst | 16 functions and macros for memory allocations. The allocation request
19 when an allocation fails and those that don't.
|
| H A D | idr.rst | 18 only ID allocation, and as a result is much more memory-efficient.
36 ID by passing a ``NULL`` pointer to the allocation function; initialise the
67 idr_preload_end() after the allocation.
|
| /linux/drivers/android/binder/range_alloc/ |
| H A D | array.rs | 247 let DescriptorState::Allocated(allocation) = &mut range.state else { in reserve_existing()
251 let data = allocation.take(); in reserve_existing()
252 let debug_id = allocation.reservation.debug_id; in reserve_existing()
253 range.state = DescriptorState::Reserved(allocation.reservation.clone()); in reserve_existing()
259 if let DescriptorState::Allocated(allocation) = &mut range.state { in take_for_each()
263 allocation.reservation.debug_id, in take_for_each()
264 allocation.data.take(), in take_for_each()
|
| H A D | tree.rs | 338 Some((DescriptorState::Allocated(allocation), free_node_res)) => { in reserve_existing()
339 let (reservation, data) = allocation.deallocate(); in reserve_existing()
363 if let Some((DescriptorState::Allocated(allocation), _)) = &mut desc.state { in take_for_each()
367 allocation.debug_id(), in take_for_each()
368 allocation.take(), in take_for_each()
|
| /linux/Documentation/mm/ |
| H A D | allocation-profiling.rst | 23 When set to "never", memory allocation profiling overhead is minimized and it
30 If compression fails, a warning is issued and memory allocation profiling gets
67 Memory allocation profiling builds off of code tagging, which is a library for
72 To add accounting for an allocation call, we replace it with a macro
76 - calls the real allocation function
81 do not properly belong to the outer allocation context and should be counted
85 Thus, proper usage requires determining which function in an allocation call
92 - switch its allocation call to the _noprof() version, e.g. kmalloc_noprof()
108 - Hook your data structure's init function, like any other allocation function.
|
| H A D | page_frags.rst | 11 simple allocation framework for page fragments. This is used by the
17 cache is needed. This provides a central point for the fragment allocation
20 which can be expensive at allocation time. However due to the nature of
23 to be disabled when executing the fragment allocation.
26 allocation. The netdev_alloc_cache is used by callers making use of the
41 avoid calling get_page per allocation.
|
| H A D | page_owner.rst | 10 When allocation happens, information about allocation such as call stack
15 Although we already have tracepoint for tracing page allocation/free,
30 allocation and free operation. It's also possible to show only a numeric
41 the page allocator hotpath and if not enabled, then allocation is done
43 not affect to allocation performance, especially if the static keys jump
185 -a Sort by memory allocation time.
251 st stacktrace stack trace of the page allocation
264 st stacktrace stack trace of the page allocation
|
| /linux/Documentation/filesystems/ext4/ |
| H A 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/drivers/android/binder/ |
| H A D | transaction.rs | 17 allocation::{Allocation, TranslatedFds},
73 allocation: SpinLock<Option<Allocation>>, field
142 allocation <- kernel::new_spinlock!(Some(alloc.success()), "Transaction::new"), in new()
179 allocation <- kernel::new_spinlock!(Some(alloc.success()), "Transaction::new"), in new_reply()
291 let mut alloc_guard = t_outdated.allocation.lock(); in submit()
372 let mut alloc = self.allocation.lock().take().ok_or(ESRCH)?; in prepare_file_list()
376 *self.allocation.lock() = Some(alloc); in prepare_file_list()
448 let mut alloc = self.allocation.lock().take().ok_or(ESRCH)?; in do_work()
475 let allocation = self.allocation.lock().take(); in cancel() localVariable
476 drop(allocation); in cancel()
|
| /linux/drivers/md/dm-vdo/ |
| H A D | dump.c | 163 wait_on, data_vio, data_vio->allocation.pbn, data_vio->logical.lbn, in dump_vio_waiters()
169 data_vio, data_vio->allocation.pbn, data_vio->logical.lbn, in dump_vio_waiters()
239 data_vio->allocation.pbn, data_vio->logical.lbn, in dump_data_vio()
244 data_vio->allocation.pbn, data_vio->logical.lbn); in dump_data_vio()
|
| /linux/tools/testing/memblock/ |
| H A D | README | 17 allocation functionalities of memblock. The main data structure of the boot time
58 allocation functions. Tests for each group are defined in dedicated files, as it
82 Some allocation functions clear the memory in the process, so it is required for
85 points to a block of memory allocated via malloc. For each group of allocation
87 at the end of the test run. The structure of a test runner checking allocation
95 (...allocation checks...)
|
| /linux/Documentation/admin-guide/ |
| H A 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/Documentation/driver-api/cxl/allocation/ |
| H A D | page-allocator.rst | 7 The kernel page allocator services all general page allocation requests, such
32 available and compatible ZONE for an allocation from the local node first.
34 An example of a `zone incompatibility` is attempting to service an allocation
46 Finally, assuming CXL memory is reachable via the page allocation (i.e. onlined
|
| H A D | hugepages.rst | 29 allocation.
32 Page allocation.
|
| /linux/drivers/soundwire/ |
| H A D | Makefile | 11 soundwire-generic-allocation-objs := generic_bandwidth_allocation.o
12 obj-$(CONFIG_SOUNDWIRE_GENERIC_ALLOCATION) += soundwire-generic-allocation.o
|
| /linux/arch/powerpc/platforms/powernv/ |
| H A D | Kconfig | 32 bool "Enable runtime allocation of RAM for tracing"
35 Enabling this option allows for runtime allocation of memory (RAM)
|
| /linux/Documentation/translations/zh_CN/core-api/ |
| H A D | memory-allocation.rst | 3 :Original: Documentation/core-api/memory-allocation.rst
13 .. _cn_core-api_memory-allocation:
|
| /linux/scripts/coccinelle/null/ |
| H A 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/tools/testing/selftests/cgroup/ |
| H A D | test_zswap.c | 530 void *allocation; in test_no_kmem_bypass()
532 allocation = malloc(values->target_alloc_bytes); in test_no_kmem_bypass()
533 if (!allocation) { in test_no_kmem_bypass()
538 ((char *)allocation)[i] = 'a'; in test_no_kmem_bypass()
541 free(allocation); in test_no_kmem_bypass()
551 * a very high value so that the allocation falls below low wm, then makes in test_no_kmem_bypass()
552 * another allocation to trigger kswapd that should push the memcg-owned pages in test_no_kmem_bypass()
685 /* Notify parent that allocation and pageout are done */
467 void *allocation; no_kmem_bypass_child() local
|
| /linux/Documentation/translations/it_IT/core-api/ |
| H A D | memory-allocation.rst | 3 :Original: :ref:`Documentation/core-api/memory-allocation.rst <memory_allocation>`
|
| /linux/Documentation/driver-api/ |
| H A D | sm501.rst | 41 The centralised memory allocation allows the driver to ensure that the
42 maximum possible resource allocation can be made to the video subsystem
45 The primary issue with memory allocation is that of moving the video
|
| /linux/Documentation/userspace-api/ |
| H A D | dma-buf-alloc-exchange.rst | 180 described as having a height of 1080, with the memory allocation for each buffer
233 buffer-allocation interface available at either kernel or userspace level, the
234 client makes an arbitrary choice of allocation interface such as Vulkan, GBM, or
237 Each allocation request must take, at a minimum: the pixel format, a list of
239 this set of properties in different ways, such as allowing allocation in more
244 allocation, any padding required, and further properties of the underlying
250 After allocation, the client must query the allocator to determine the actual
272 memory. For this reason, each import and allocation API must provide a separate
314 In the latter case, the allocation is as discussed above, being provided with a
343 - during allocation, a user may supply ``DRM_FORMAT_MOD_INVALID``, either as the
[all …]
|