Searched refs:allocations (Results 1 – 25 of 95) sorted by relevance
1234
| /Linux-v5.4/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-v5.4/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
105 For large allocations you can use :c:func:`vmalloc` and
|
| 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 | gfp_mask-from-fs-io.rst | 59 GFP_KERNEL allocations deep inside the allocator which are quite non-trivial
|
| /Linux-v5.4/drivers/staging/netlogic/ |
| D | TODO | 2 * All memory allocation should be changed to DMA allocations
|
| /Linux-v5.4/drivers/acpi/acpica/ |
| D | dbexec.c | 350 u32 allocations; in acpi_db_execute() local
426 allocations = in acpi_db_execute()
431 if (allocations > 0) { in acpi_db_execute()
434 allocations, acpi_gbl_db_method_info.pathname); in acpi_db_execute()
|
| /Linux-v5.4/arch/arc/ |
| D | Kconfig.debug | 10 on the VM subsystem for higher order allocations.
|
| /Linux-v5.4/arch/xtensa/boot/dts/ |
| D | kc705.dts | 21 /* global autoconfigured region for contiguous allocations */
|
| /Linux-v5.4/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
|
| /Linux-v5.4/Documentation/vm/ |
| 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 | 31 allocations will be available in the future without having to
|
| /Linux-v5.4/Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smem.txt | 25 Definition: reference to a hwspinlock used to protect allocations from
|
| /Linux-v5.4/Documentation/admin-guide/sysctl/ |
| D | vm.rst | 262 the system. Values tending towards 0 imply allocations would fail due to lack
322 So the Linux page allocator has a mechanism which prevents allocations
328 mechanism will also defend that region from allocations which could use
462 allocations; if you set this to lower than 1024KB, your system will
521 resulting from mmap allocations on architectures which support
534 resulting from mmap allocations for applications run in
575 NOMMU mmap allocations.
577 A value of 0 disables trimming of allocations entirely, while a value of 1
579 trimming of allocations is initiated.
625 On 32-bit, the Normal zone needs to be preserved for allocations accessible
[all …]
|
| /Linux-v5.4/security/selinux/include/ |
| D | avc.h | 39 unsigned int allocations; member
|
| /Linux-v5.4/lib/ |
| D | Kconfig.kasan | 53 and introduces an overhead of ~x1.5 for the rest of the allocations.
72 and introduces an overhead of ~20% for the rest of the allocations.
|
| /Linux-v5.4/Documentation/admin-guide/mm/ |
| 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-v5.4/drivers/staging/qlge/ |
| D | TODO | 11 while containing two frags of order-1 allocations, ie. >16K)
|
| /Linux-v5.4/Documentation/fault-injection/ |
| D | fault-injection.rst | 126 highmem/user allocations.
134 only into non-sleep allocations (GFP_ATOMIC allocations).
|
| /Linux-v5.4/Documentation/x86/x86_64/ |
| D | fake-numa-for-cpusets.rst | 54 memory allocations (1G).
|
| /Linux-v5.4/arch/sh/ |
| D | Kconfig.debug | 36 on the VM subsystem for higher order allocations. This option
|
| /Linux-v5.4/Documentation/scsi/ |
| D | ChangeLog.ips | 40 4.71.00 - Change all memory allocations to not use GFP_DMA flag
|
| /Linux-v5.4/Documentation/filesystems/ext4/ |
| D | allocators.rst | 21 unused speculative allocations are of course freed, but if the
|
1234
