Lines Matching refs:allocations

284 the system. Values tending towards 0 imply allocations would fail due to lack
318 This is useful for workloads that require low latency memory allocations
319 and have a bounded burstiness in memory allocations, for example a
321 (causing in-kernel memory allocations) with a maximum total message burst
359 So the Linux page allocator has a mechanism which prevents allocations
365 mechanism will also defend that region from allocations which could use
499 allocations; if you set this to lower than 1024KB, your system will
558 resulting from mmap allocations on architectures which support
571 resulting from mmap allocations for applications run in
612 NOMMU mmap allocations.
614 A value of 0 disables trimming of allocations entirely, while a value of 1
616 trimming of allocations is initiated.
662 On 32-bit, the Normal zone needs to be preserved for allocations accessible
951 increase the success rate of future high-order allocations such as SLUB
952 allocations, THP and hugetlbfs pages.
1017 Allowing regular swap effectively restricts allocations to the local