Lines Matching refs:huge
11 preallocated for application use. These huge pages are instantiated in a
12 task's address space at page fault time if the VMA indicates huge pages are
13 to be used. If no huge page exists at page fault time, the task is sent
14 a SIGBUS and often dies an unhappy death. Shortly after huge page support
16 of huge pages at mmap() time. The idea is that if there were not enough
17 huge pages to cover the mapping, the mmap() would fail. This was first
19 were enough free huge pages to cover the mapping. Like most things in the
21 'reserve' huge pages at mmap() time to ensure that huge pages would be
23 describe how huge page reserve processing is done in the v4.10 kernel.
36 This is a global (per-hstate) count of reserved huge pages. Reserved
37 huge pages are only available to the task which reserved them.
38 Therefore, the number of huge pages generally available is computed
52 There is one reserve map for each huge page mapping in the system.
62 The 'from' and 'to' fields of the file region structure are huge page
77 The PagePrivate page flag is used to indicate that a huge page
78 reservation must be restored when the huge page is freed. More
79 details will be discussed in the "Freeing huge pages" section.
85 A huge page mapping or segment is either private or shared. If private,
103 Reservations are created when a huge page backed shared memory segment is
117 The arguments 'from' and 'to' are huge page indices into the mapping or
139 The reservation map is consulted to determine how many huge page reservations
156 are enough free huge pages to accommodate the reservation. If there are,
166 If there were enough free huge pages and the global count resv_huge_pages
182 Reservations are consumed when huge pages associated with the reservations
229 Note, if no huge page can be found that satisfies the VMA's memory policy
231 brings up the issue of surplus huge pages and overcommit which is beyond
236 After obtaining a new huge page, (page)->private is set to the value of
264 After huge page allocation, the page is typically added to the page tables
268 when a huge page that has been instantiated is freed no adjustment is made
277 passed a pointer to the page struct. When a huge page is freed, reservation
302 There is a struct hstate associated with each huge page size. The hstate
303 tracks all huge pages of the specified size. A subpool represents a subset
308 which indicates the minimum number of huge pages required by the filesystem.
309 If this option is specified, the number of huge pages corresponding to
313 huge pages. If they can not be reserved, the mount fails.
318 hugepage_subpool_get/put_pages are passed the number of huge pages by which
326 suppose a subpool contains 3 reserved huge pages and someone asks for 5.
345 COW, it is possible that no free huge pages are free and the allocation
389 there are enough huge pages for the operation to succeed.
427 - When a hole is being punched in a hugetlbfs file. In this case, huge pages
444 region_count() is called when unmapping a private huge page mapping. In
458 These routines are only interested with reservations for a specific huge
522 Additionally, after a huge page is instantiated the PagePrivate flag is
525 However, there are several instances where errors are encountered after a huge
532 will cause the 'leak' of a reserved huge page. The global reserve count will
551 so that a reservation will not be leaked when the huge page is freed.
556 Per-node huge page lists existed in struct hstate when git was first used
583 of cpusets or memory policy there is no guarantee that huge pages will be