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…
44 hugetlb.64KB.limit_in_bytes
45 hugetlb.64KB.max_usage_in_bytes
46 hugetlb.64KB.usage_in_bytes
47 hugetlb.64KB.failcnt
48 hugetlb.64KB.rsvd.limit_in_bytes
49 hugetlb.64KB.rsvd.max_usage_in_bytes
50 hugetlb.64KB.rsvd.usage_in_bytes
51 hugetlb.64KB.rsvd.failcnt
62 1. Page fault accounting
69 The HugeTLB controller allows users to limit the HugeTLB usage (page fault) per
70 control group and enforces the limit during page fault. Since HugeTLB
71 doesn't support page reclaim, enforcing the limit at page fault time implies
95 Reservation limits are superior to page fault limits described above, since
99 non-HugeTLB memory for example. In the case of page fault accounting, it's very
103 systems is practically impossible with page fault accounting.
108 For shared HugeTLB memory, both HugeTLB reservation and page faults are charged
117 4. Caveats with HugeTLB cgroup offline.
122 - The fault charges are charged to the parent HugeTLB cgroup (reparented),
123 - the reservation charges remain on the offline HugeTLB cgroup.