Lines Matching +full:4 +full:kb +full:- +full:page
7 # mount -t cgroup -o hugetlb none /sys/fs/cgroup
25 …rsvd.max_usage_in_bytes # show max "hugepagesize" hugetlb reservations and no-reserve faults
26 …hugetlb.<hugepagesize>.rsvd.usage_in_bytes # show current reservations and no-reserve f…
46 hugetlb.64KB.limit_in_bytes
47 hugetlb.64KB.max_usage_in_bytes
48 hugetlb.64KB.numa_stat
49 hugetlb.64KB.usage_in_bytes
50 hugetlb.64KB.failcnt
51 hugetlb.64KB.rsvd.limit_in_bytes
52 hugetlb.64KB.rsvd.max_usage_in_bytes
53 hugetlb.64KB.rsvd.usage_in_bytes
54 hugetlb.64KB.rsvd.failcnt
66 1. Page fault accounting
75 The HugeTLB controller allows users to limit the HugeTLB usage (page fault) per
76 control group and enforces the limit during page fault. Since HugeTLB
77 doesn't support page reclaim, enforcing the limit at page fault time implies
103 Reservation limits are superior to page fault limits described above, since
107 non-HugeTLB memory for example. In the case of page fault accounting, it's very
111 systems is practically impossible with page fault accounting.
116 For shared HugeTLB memory, both HugeTLB reservation and page faults are charged
125 4. Caveats with HugeTLB cgroup offline.
130 - The fault charges are charged to the parent HugeTLB cgroup (reparented),
131 - the reservation charges remain on the offline HugeTLB cgroup.