Searched refs:allocations (Results 1 – 25 of 107) sorted by relevance
12345
| /Linux-v6.1/tools/perf/Documentation/ |
| D | examples.txt | 66 well. For example the page allocations done by a 'git gc' can be
77 To check which functions generated page allocations:
120 allocations - to see precisely what kind of page allocations there
157 Or you can observe the whole system's page allocations for 10
173 Or observe how fluctuating the page allocations are, via statistical
190 and check which instructions/source-code generated page allocations:
209 ( this shows that 83.42% of __GI___fork's page allocations come from
|
| /Linux-v6.1/lib/ |
| D | Kconfig.kfence | 33 allocations will be guarded by KFENCE. May be overridden via boot
49 bool "Use a deferrable timer to trigger allocations"
51 Use a deferrable timer to trigger allocations. This avoids forcing
61 bool "Use static keys to set up allocations" if EXPERT
64 Use static keys (static branches) to set up KFENCE allocations. This
82 and allocations/frees. A value of 0 disables stress testing logic.
|
| D | Kconfig.kasan | 80 overhead of ~50% for dynamic allocations.
99 add an overhead of ~20% for dynamic allocations.
171 bool "Check accesses to vmalloc allocations"
174 Makes KASAN check the validity of accesses to vmalloc allocations.
176 With software KASAN modes, all types vmalloc allocations are
|
| /Linux-v6.1/Documentation/core-api/ |
| D | memory-allocation.rst | 41 many other allocations types can use ``GFP_KERNEL``. Note, that
52 * Untrusted allocations triggered from userspace should be a subject
55 allocations that should be accounted.
56 * Userspace allocations should use either of the ``GFP_USER``,
72 You may notice that quite a few allocations in the existing code
89 Memory allocations may trigger direct or background reclaim and it is
154 For large allocations you can use vmalloc() and vzalloc(), or directly
|
| D | genalloc.rst | 27 allocations is set with min_alloc_order; it is a log-base-2 number like
29 So, if min_alloc_order is passed as 3, then all allocations will be a
44 It's worth noting that, if there are still allocations outstanding from the
60 pool, once again using nid as the node ID for ancillary memory allocations.
63 for DMA allocations.
|
| D | boot-time-mm.rst | 16 functions and macros for memory allocations. The allocation request
|
| D | maple_tree.rst | 91 The allocations are handled by the internal tree code. See
196 Allocations are usually handled internally to the tree, however if allocations
201 unused allocations.
|
| /Linux-v6.1/Documentation/dev-tools/ |
| D | kfence.rst | 39 sample interval determines the frequency with which heap allocations will be
44 The sample interval controls a timer that sets up KFENCE allocations. By
57 further KFENCE allocations occur. With ``CONFIG_KFENCE_NUM_OBJECTS`` (default
242 Guarded allocations are set up based on the sample interval. After expiration
248 When using ``CONFIG_KFENCE_STATIC_KEYS=y``, KFENCE allocations are "gated"
290 coverage of allocations, KFENCE limits currently covered allocations of the
293 limits frequent long-lived allocations (e.g. pagecache) of the same source
296 at which to start limiting currently covered allocations can be configured via
303 page handling code to set up and deal with KFENCE allocations.
|
| /Linux-v6.1/drivers/acpi/acpica/ |
| D | dbexec.c | 353 u32 allocations; in acpi_db_execute() local
446 allocations = in acpi_db_execute()
451 if (allocations > 0) { in acpi_db_execute()
454 allocations, acpi_gbl_db_method_info.pathname); in acpi_db_execute()
|
| /Linux-v6.1/arch/arc/ |
| D | Kconfig.debug | 10 on the VM subsystem for higher order allocations.
|
| /Linux-v6.1/arch/xtensa/boot/dts/ |
| D | kc705.dts | 21 /* global autoconfigured region for contiguous allocations */
|
| /Linux-v6.1/Documentation/mm/ |
| D | numa.rst | 82 memory, Linux must decide whether to order the zonelists such that allocations
124 So, default, local allocations will succeed with the kernel supplying the
126 allows such allocations to fallback to other nearby nodes when a node that
129 Some kernel allocations do not want or cannot tolerate this allocation fallback
150 allocations will be attempted.
|
| D | balance.rst | 10 well as for non __GFP_IO allocations.
67 for non-sleepable allocations. Second, the HIGHMEM zone is also balanced,
69 HIGHMEM page, as well as to ensure that HIGHMEM allocations do not
|
| D | z3fold.rst | 14 * unlike zbud, z3fold allows for up to PAGE_SIZE allocations
|
| D | overcommit-accounting.rst | 29 allocations will be available in the future without having to
|
| /Linux-v6.1/mm/ |
| D | Kconfig.debug | 12 bool "Debug page memory allocations"
42 bool "Enable debug page memory allocations by default?"
45 Enable debug page memory allocations by default? This value
49 bool "Debug slab memory allocations"
|
| /Linux-v6.1/Documentation/networking/ |
| D | page_pool.rst | 134 * ``fast``: successful fast path allocations
135 * ``slow``: slow path order-0 allocations
136 * ``slow_high_order``: slow path high order allocations
|
| /Linux-v6.1/Documentation/admin-guide/mm/ |
| D | memory-hotplug.rst | 220 movable pages off the affected memory block. As most kernel allocations, such as
505 allocations.
541 Most kernel allocations are unmovable. Important examples include the memory
542 map (usually 1/64ths of memory), page tables, and kmalloc(). Such allocations
546 movable. Such allocations can be served from ZONE_MOVABLE and the kernel zones.
548 Only movable allocations are served from ZONE_MOVABLE, resulting in unmovable
549 allocations being limited to the kernel zones. Without ZONE_MOVABLE, there is
557 might crash because it runs out of free memory for unmovable allocations,
593 allocations and silently create a zone imbalance, usually triggered by
|
| D | numa_memory_policy.rst | 37 that governs all page allocations that aren't controlled by
42 allocations across all nodes with "sufficient" memory, so as
44 allocations.
48 specific task, this policy controls all page allocations made
51 all page allocations that would have been controlled by the
146 allocations of page cache pages for regular files mmap()ed
223 This mode specifies that page allocations be interleaved, on a
|
| /Linux-v6.1/security/selinux/include/ |
| D | avc.h | 39 unsigned int allocations; member
|
| /Linux-v6.1/Documentation/admin-guide/sysctl/ |
| D | vm.rst | 276 the system. Values tending towards 0 imply allocations would fail due to lack
336 So the Linux page allocator has a mechanism which prevents allocations
342 mechanism will also defend that region from allocations which could use
476 allocations; if you set this to lower than 1024KB, your system will
535 resulting from mmap allocations on architectures which support
548 resulting from mmap allocations for applications run in
626 NOMMU mmap allocations.
628 A value of 0 disables trimming of allocations entirely, while a value of 1
630 trimming of allocations is initiated.
676 On 32-bit, the Normal zone needs to be preserved for allocations accessible
[all …]
|
| /Linux-v6.1/drivers/staging/qlge/ |
| D | TODO | 8 while containing two frags of order-1 allocations, ie. >16K)
|
| /Linux-v6.1/Documentation/fault-injection/ |
| D | fault-injection.rst | 136 highmem/user allocations (__GFP_HIGHMEM allocations).
144 into allocations that can sleep (__GFP_DIRECT_RECLAIM allocations).
|
| /Linux-v6.1/drivers/staging/media/atomisp/ |
| D | notes.txt | 10 address. The hmm code keeps a list of all allocations and when necessary
|
| /Linux-v6.1/Documentation/gpu/rfc/ |
| D | i915_vm_bind.rst | 140 `Evictable page table allocations`_) and are maintained per VM and needs to
228 Evictable page table allocations
230 Make pagetable allocations evictable and manage them similar to VM_BIND
|
12345
