linux-master/mm/hugetlb.c

36 #include <linux/memory.h>
417 		 * performance enhancement and memory saving issue.
927  * A rare out of memory error was encountered which prevented removal of
1658 	 * pages.  Otherwise, someone (memory error handling) may try to write
1874 		 * hugetlb pages with vmemmap we will free up memory so that we
1891 		 * memory).  If unable to restore a hugetlb page, the hugetlb
2385  *           when the system is under memory pressure and the feature of
2468  * Dissolve free hugepages in a given pfn range. Used by memory hotplug to
2469  * make specified memory blocks removable from the system.
2738 	 * evenly across all nodes with memory. Iterate across these nodes
2742 	 * on-line nodes with memory and will handle the hstate accounting.
2935 			 * Rare out of memory condition in reserve map
2963 				 * VERY rare out of memory condition.  Since
2973 			 * Rare out of memory condition from
3428 		 * in order to fix confusing memory reports from free(1) and
4506  * devices of nodes that have memory.  All on-line nodes should have
5106 /* Return the number pages of memory we physically have, in PAGE_SIZE units. */
5134 	 * task or memory node can be dynamically moved between cpusets.
5142 	 * Apart from cpuset, we also have memory policy mechanism that
5143 	 * also determines from which node the kernel will allocate memory
5145 	 * the memory policy of the current task. Similar to the description
5282  * This is because under System V memory model, mappings created via
6318 		 * If memory error occurs between mmap() and fault, some process
6778 	 * If we just allocated a new page, we need a memory barrier to ensure
6780 	 * set_pte_at() write. The memory barrier inside __folio_mark_uptodate
7671  * within the specific vma for a hugetlbfs memory range.