Searched refs:hugepage (Results 1 – 16 of 16) sorted by relevance
| /linux-4.4.14/mm/ |
| D | hugetlb_cgroup.c | 27 struct page_counter hugepage[HUGE_MAX_HSTATE]; member
64 if (page_counter_read(&h_cg->hugepage[idx])) in hugetlb_cgroup_have_usage()
83 page_counter_init(&h_cgroup->hugepage[idx], in hugetlb_cgroup_css_alloc()
84 &parent_h_cgroup->hugepage[idx]); in hugetlb_cgroup_css_alloc()
88 page_counter_init(&h_cgroup->hugepage[idx], NULL); in hugetlb_cgroup_css_alloc()
130 page_counter_charge(&parent->hugepage[idx], nr_pages); in hugetlb_cgroup_move_parent()
132 counter = &h_cg->hugepage[idx]; in hugetlb_cgroup_move_parent()
189 if (!page_counter_try_charge(&h_cg->hugepage[idx], nr_pages, &counter)) in hugetlb_cgroup_charge_cgroup()
224 page_counter_uncharge(&h_cg->hugepage[idx], nr_pages); in hugetlb_cgroup_uncharge_page()
237 page_counter_uncharge(&h_cg->hugepage[idx], nr_pages); in hugetlb_cgroup_uncharge_cgroup()
[all …]
|
| D | mempolicy.c | 1960 unsigned long addr, int node, bool hugepage) in alloc_pages_vma() argument
1981 if (unlikely(IS_ENABLED(CONFIG_TRANSPARENT_HUGEPAGE) && hugepage)) { in alloc_pages_vma()
|
| /linux-4.4.14/tools/testing/selftests/vm/ |
| D | .gitignore | 1 hugepage-mmap
2 hugepage-shm
|
| D | Makefile | 5 BINARIES += hugepage-mmap
6 BINARIES += hugepage-shm
|
| D | run_vmtests | 55 ./hugepage-mmap
70 ./hugepage-shm
|
| /linux-4.4.14/Documentation/vm/ |
| D | transhuge.txt | 39 hugepage knowledge fall back to breaking a transparent hugepage and
43 - if a hugepage allocation fails because of memory fragmentation,
56 is not specific to transparent hugepage support and it's a generic
67 entities). It doesn't require reservation to prevent hugepage
77 lived page allocations even for hugepage unaware applications that
149 and how many milliseconds to wait in khugepaged if there's an hugepage
269 get_user_pages and follow_page if run on a hugepage, will return the
285 hugepage backed mappings.
291 follow_page because it's not hugepage aware and in fact it can't work
301 memory region, the mmap region has to be hugepage naturally
[all …]
|
| D | hugetlbpage.txt | 192 When adjusting the persistent hugepage count via nr_hugepages_mempolicy, any
319 not hugepage aligned. For example, munmap(2) will fail if memory is backed by
320 a hugetlb page and the length is smaller than the hugepage size.
328 2) hugepage-shm: see tools/testing/selftests/vm/hugepage-shm.c
330 3) hugepage-mmap: see tools/testing/selftests/vm/hugepage-mmap.c
|
| D | hwpoison.txt | 183 - Right now hugepage support is missing.
|
| D | userfaultfd.txt | 32 Vmas are not suitable for page- (or hugepage) granular fault tracking
|
| /linux-4.4.14/Documentation/ |
| D | dontdiff | 138 hugepage-mmap
139 hugepage-shm
|
| /linux-4.4.14/arch/powerpc/mm/ |
| D | Makefile | 34 obj-$(CONFIG_TRANSPARENT_HUGEPAGE) += hugepage-hash64.o
|
| /linux-4.4.14/Documentation/cgroups/ |
| D | hugetlb.txt | 35 For a system supporting two hugepage size (16M and 16G) the control
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | vm.txt | 247 architecture and/or the hugepage size. If a hugepage supports migration,
248 allocation from ZONE_MOVABLE is always enabled for the hugepage regardless
253 this parameter is that users can make hugepage pool more extensible by
490 Change the minimum size of the hugepage pool.
498 Change the maximum size of the hugepage pool. The maximum is
|
| /linux-4.4.14/include/linux/ |
| D | gfp.h | 455 int node, bool hugepage);
|
| /linux-4.4.14/Documentation/trace/ |
| D | events-kmem.txt | 107 pageblock_size is usually the size of the default hugepage size.
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | proc.txt | 457 "AnonHugePages" shows the ammount of memory backed by transparent hugepage.
800 A page block is typically the size of the default hugepage size e.g. 2MB on
|