Lines Matching +full:current +full:- +full:limit

7 # mount -t cgroup -o hugetlb none /sys/fs/cgroup
19 The above steps create a new group g1 and move the current shell
24 …hugetlb.<hugepagesize>.rsvd.limit_in_bytes            # set/show limit of "hugepagesize" hugetlb r…
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…
27 ….failcnt                   # show the number of allocation failure due to HugeTLB reservation limit
28 …hugetlb.<hugepagesize>.limit_in_bytes                 # set/show limit of "hugepagesize" hugetlb f…
30 …hugetlb.<hugepagesize>.usage_in_bytes                 # show current usage for "hugepagesize" huge…
31 …>.failcnt                        # show the number of allocation failure due to HugeTLB usage limit
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
79 pages beyond its limit. Therefore the application needs to know exactly how many
94 The HugeTLB controller allows to limit the HugeTLB reservations per control
95 group and enforces the controller limit at reservation time and at the fault of
99 MAP_NORESERVE allocations, the reservation limit behaves the same as the fault
100 limit, enforcing memory usage at fault time and causing the application to
101 receive a SIGBUS if it's crossing its limit.
107 non-HugeTLB memory for example. In the case of page fault accounting, it's very
130 - The fault charges are charged to the parent HugeTLB cgroup (reparented),
131 - the reservation charges remain on the offline HugeTLB cgroup.