Lines Matching refs:memory

5 Performance critical computing applications dealing with large memory
8 using huge pages for the backing of virtual memory with huge pages
12 Currently it only works for anonymous memory mappings but in the
22 only matters the first time the memory is accessed for the lifetime of
23 a memory mapping. The second long lasting and much more important
24 factor will affect all subsequent accesses to the memory for the whole
29 mapping a much larger amount of virtual memory in turn reducing the
43 - if a hugepage allocation fails because of memory fragmentation,
49   immediately in the buddy or through the VM), guest physical memory
53 - it doesn't require memory reservation and in turn it uses hugepages
55   to avoid unmovable pages to fragment all the memory but such a tweak
60 - this initial support only offers the feature in the anonymous memory
64 Transparent Hugepage Support maximizes the usefulness of free memory
66 unused memory to be used as cache or other movable (or even unmovable
78 deals with large amounts of memory.
81 may end up allocating more memory resources. An application may mmap a
88 to eliminate any risk of wasting any precious byte of memory and to
92 risk to lose memory by using hugepages, should use
99 avoid the risk of consuming more memory resources) or enabled system
108 to never try to defrag memory and simply fallback to regular pages
110 time to defrag memory, we would expect to gain even more by the fact
168 A higher value leads to use additional memory for programs.
179 memory. A lower value can prevent THPs from being
181 THPs, and lower memory access performance.
237 system uses memory compaction to copy data around memory to free a
242 	memory compaction so that a huge page is free for use.
244 compact_success is incremented if the system compacted memory and
247 compact_fail is incremented if the system tries to compact memory
259 compact_blocks_moved is incremented each time memory compaction examines
296 memory in regular page sizes and with regular pte/pmd mappings).
301 memory region, the mmap region has to be hugepage naturally