| /linux/tools/perf/Documentation/ |
| H A 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/lib/ |
| H A 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.
|
| H A D | Kconfig.kasan | 101 overhead of ~50% for dynamic allocations.
118 add an overhead of ~20% for dynamic allocations.
187 bool "Check accesses to vmalloc allocations"
190 Makes KASAN check the validity of accesses to vmalloc allocations.
192 With software KASAN modes, all types vmalloc allocations are
|
| /linux/Documentation/mm/ |
| H A D | allocation-profiling.rst | 7 Low overhead (suitable for production) accounting of all memory allocations,
17 adds warnings for allocations that weren't accounted because of a
43 warnings produced by allocations made while profiling is disabled and freed
96 taking effect. This is important for allocations internal to the mm/ code that
118 Do this when you're implementing a generic data structure that does allocations
129 - Then, use the following form for your allocations:
136 KFENCE allocations are rare and limited to a small number, so this omission
|
| H A D | overcommit-accounting.rst | 28 allocations will be available in the future without having to
|
| /linux/Documentation/core-api/ |
| H A 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.
|
| H A D | memory-allocation.rst | 41 many other allocations types can use ``GFP_KERNEL``. Note, that
53 * Untrusted allocations triggered from userspace should be a subject
56 allocations that should be accounted.
57 * Userspace allocations should use either of the ``GFP_USER``,
73 You may notice that quite a few allocations in the existing code
90 Memory allocations may trigger direct or background reclaim and it is
157 For large allocations you can use vmalloc() and vzalloc(), or directly
|
| H A D | maple_tree.rst | 21 interfere with allocations in a low memory situation.
47 data density, erasing an entry may cause allocations to occur. That is,
77 mtree_erase() may use GFP_KERNEL | __GFP_NOFAIL for allocations and cannot
107 The allocations are handled by the internal tree code. See
216 Allocations are usually handled internally to the tree, however if allocations
221 unused allocations.
|
| H A D | boot-time-mm.rst | 16 functions and macros for memory allocations. The allocation request
|
| /linux/drivers/acpi/acpica/ |
| H A 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/arch/arc/ |
| H A D | Kconfig.debug | 10 on the VM subsystem for higher order allocations.
|
| /linux/arch/xtensa/boot/dts/ |
| H A D | kc705.dts | 21 /* global autoconfigured region for contiguous allocations */
|
| /linux/mm/ |
| H A 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
256 allocations. See Documentation/dev-tools/kmemleak.rst for more
271 Kmemleak must track all the memory allocations to avoid
276 if slab allocations fail.
|
| H A D | Kconfig | 223 specifically-sized allocations with user-controlled contents
227 user-controlled allocations. This may very slightly increase
229 of extra pages since the bulk of user-controlled allocations
253 caches for normal kmalloc allocations. This makes it more difficult
329 allocations to compliment SLAB_FREELIST_RANDOM, but the
433 # allocations when sparse_init() is called. If this cannot
637 allocations (e.g., ZONE_MOVABLE, CMA) and such that they can be
985 allocations, such as transparent huge pages.
1098 # the max page order for physically contiguous allocations.
|
| /linux/Documentation/driver-api/cxl/linux/ |
| H A D | memory-hotplug.rst | 34 migratable allocations.
51 The location of :code:`struct folio` allocations to represent the hotplugged
|
| /linux/security/selinux/include/ |
| H A D | avc.h | 40 unsigned int allocations; member
|
| /linux/arch/nios2/ |
| H A D | Kconfig | 51 int "Order of maximal physically contiguous allocations"
55 contiguous allocations. The limit is called MAX_PAGE_ORDER and it
|
| /linux/arch/sh/mm/ |
| H A D | Kconfig | 34 int "Order of maximal physically contiguous allocations"
41 contiguous allocations. The limit is called MAX_PAGE:_ORDER and it
|
| /linux/drivers/staging/media/atomisp/ |
| H A D | notes.txt | 10 address. The hmm code keeps a list of all allocations and when necessary
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-mm-mempolicy-weighted-interleave | 15 These weights only affect new allocations, and changes at runtime
|
| /linux/Documentation/driver-api/cxl/allocation/ |
| H A D | page-allocator.rst | 35 marked :code:`GFP_KERNEL` from :code:`ZONE_MOVABLE`. Kernel allocations are
|
| /linux/Documentation/gpu/rfc/ |
| H A 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
|
| /linux/fs/nfsd/ |
| H A D | filecache.c | 1470 unsigned long allocations = 0, releases = 0, evictions = 0; in nfsd_file_cache_stats_show() local
1495 allocations += per_cpu(nfsd_file_allocations, i); in nfsd_file_cache_stats_show()
1506 seq_printf(m, "allocations: %lu\n", allocations); in nfsd_file_cache_stats_show()
|
| /linux/arch/arm64/boot/dts/freescale/ |
| H A D | tqma8xx.dtsi | 34 * global autoconfigured region for contiguous allocations
|
| /linux/scripts/coccinelle/api/ |
| H A D | kmalloc_objs.cocci | 2 /// Use kmalloc_obj family of macros for allocations
|