| /linux/drivers/gpu/drm/amd/display/dc/dml2_0/dml21/src/dml2_top/ |
| H A D | dml2_top_soc15.c | 73 …l->test_mcache.assign_global_mcache_ids_params.allocations = params->display_config->stage2.mcache… in dml2_top_optimization_test_function_mcache()
657 if (!params->allocations[i].valid) in dml2_top_mcache_assign_global_mcache_ids()
660 for (j = 0; j < params->allocations[i].num_mcaches_plane0; j++) { in dml2_top_mcache_assign_global_mcache_ids()
661 params->allocations[i].global_mcache_ids_plane0[j] = next_unused_cache_id++; in dml2_top_mcache_assign_global_mcache_ids()
663 for (j = 0; j < params->allocations[i].num_mcaches_plane1; j++) { in dml2_top_mcache_assign_global_mcache_ids()
664 params->allocations[i].global_mcache_ids_plane1[j] = next_unused_cache_id++; in dml2_top_mcache_assign_global_mcache_ids()
668 params->allocations[i].global_mcache_ids_plane0[params->allocations[i].num_mcaches_plane0] = in dml2_top_mcache_assign_global_mcache_ids()
669 params->allocations[i].global_mcache_ids_plane0[0]; in dml2_top_mcache_assign_global_mcache_ids()
670 params->allocations[i].global_mcache_ids_plane1[params->allocations[i].num_mcaches_plane1] = in dml2_top_mcache_assign_global_mcache_ids()
671 params->allocations[i].global_mcache_ids_plane1[0]; in dml2_top_mcache_assign_global_mcache_ids()
[all …]
|
| /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
80 taking effect. This is important for allocations internal to the mm/ code that
102 Do this when you're implementing a generic data structure that does allocations
113 - Then, use the following form for your allocations:
|
| H A D | numa.rst | 80 memory, Linux must decide whether to order the zonelists such that allocations
122 So, default, local allocations will succeed with the kernel supplying the
124 allows such allocations to fallback to other nearby nodes when a node that
127 Some kernel allocations do not want or cannot tolerate this allocation fallback
148 allocations will be attempted.
|
| H A D | balance.rst | 8 well as for non __GFP_IO allocations.
65 for non-sleepable allocations. Second, the HIGHMEM zone is also balanced,
67 HIGHMEM page, as well as to ensure that HIGHMEM allocations do not
|
| H A D | physical_memory.rst | 220 that allocations are preferred from. The ``node_zonelists`` is set up by
258 allocations.
361 management system. By handling most frequent allocations and frees locally on
403 The number of pages which are reserved for high-order atomic allocations.
410 allocations. For example, if the highest zone a memory allocation can
414 allocator uses to prevent allocations which could use ``highmem`` from using
433 ``setup_zone_pageset()``. By handling most frequent allocations and frees
|
| /linux/Documentation/dev-tools/ |
| H A 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 interval. *Burst mode* allows to sample successive heap allocations, where the
59 denotes the *additional* successive allocations within a sample interval;
60 setting ``kfence.burst=N`` means that ``1 + N`` successive allocations are
64 further KFENCE allocations occur. With ``CONFIG_KFENCE_NUM_OBJECTS`` (default
249 Guarded allocations are set up based on the sample interval. After expiration
255 When using ``CONFIG_KFENCE_STATIC_KEYS=y``, KFENCE allocations are "gated"
297 coverage of allocations, KFENCE limits currently covered allocations of the
300 limits frequent long-lived allocations (e.g. pagecache) of the same source
[all …]
|
| /linux/Documentation/core-api/kho/ |
| H A D | index.rst | 51 allocations before during boot up to the initialization of the page allocator.
55 after kexec these regions will be used by early memory allocations, there is a
56 scratch region per NUMA node plus a scratch region to satisfy allocations
70 for boot memory allocations and as target memory for kexec blobs, some parts
|
| /linux/Documentation/core-api/ |
| 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 | 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 | 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/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.
|
| /linux/arch/arc/ |
| H A D | Kconfig.debug | 10 on the VM subsystem for higher order allocations.
|
| /linux/Documentation/driver-api/cxl/linux/ |
| H A D | early-boot.rst | 58 :code:`ZONE_NORMAL`, making it available for use for most allocations (including
67 kernel allocations (such as :code:`struct page` or page tables). This may
134 cannot be used to guarantee huge page allocations. If enabling CXL memory as
|
| H A D | memory-hotplug.rst | 34 migratable allocations.
51 The location of :code:`struct folio` allocations to represent the hotplugged
|
| /linux/arch/xtensa/boot/dts/ |
| H A D | kc705.dts | 21 /* global autoconfigured region for contiguous allocations */
|
| /linux/Documentation/admin-guide/sysctl/ |
| H A D | vm.rst | 333 the system. Values tending towards 0 imply allocations would fail due to lack
386 So the Linux page allocator has a mechanism which prevents allocations
392 mechanism will also defend that region from allocations which could use
488 memory allocations.
493 warnings produced by allocations made while profiling is disabled and freed
545 allocations; if you set this to lower than 1024KB, your system will
604 resulting from mmap allocations on architectures which support
617 resulting from mmap allocations for applications run in
722 NOMMU mmap allocations.
724 A value of 0 disables trimming of allocations entirely, while a value of 1
[all …]
|
| /linux/Documentation/admin-guide/mm/ |
| H A D | memory-hotplug.rst | 218 movable pages off the affected memory block. As most kernel allocations, such as
524 allocations.
560 Most kernel allocations are unmovable. Important examples include the memory
561 map (usually 1/64ths of memory), page tables, and kmalloc(). Such allocations
565 movable. Such allocations can be served from ZONE_MOVABLE and the kernel zones.
567 Only movable allocations are served from ZONE_MOVABLE, resulting in unmovable
568 allocations being limited to the kernel zones. Without ZONE_MOVABLE, there is
576 might crash because it runs out of free memory for unmovable allocations,
612 allocations and silently create a zone imbalance, usually triggered by
|
| H A D | kho.rst | 79 handed over memory allocations.
94 allocations. Kexec user space tools can use this file to determine
|
| /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/Documentation/admin-guide/perf/ |
| H A D | mrvl-odyssey-tad-pmu.rst | 17 allocations, interface retry rate, internal resource occupancy, etc.
|