Lines Matching +full:shared +full:- +full:memory

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…
32 …uma_stat                      # show the numa information of the hugetlb memory charged to this cg…
96 HugeTLB memory for which no reservation exists. Since reservation limits are
98 the application to get SIGBUS signal if the memory was reserved before hand. For
100 limit, enforcing memory usage at fault time and causing the application to
105 never causes the application to get SIGBUS signal if the memory was reserved
107 non-HugeTLB memory for example. In the case of page fault accounting, it's very
114 3. Caveats with shared memory
116 For shared HugeTLB memory, both HugeTLB reservation and page faults are charged
117 to the first task that causes the memory to be reserved or faulted, and all
118 subsequent uses of this reserved or faulted memory is done without charging.
120 Shared HugeTLB memory is only uncharged when it is unreserved or deallocated.
130 - The fault charges are charged to the parent HugeTLB cgroup (reparented),
131 - the reservation charges remain on the offline HugeTLB cgroup.
136 the memory controller whose cgroups also persist as zombie until all charged
137 memory is uncharged. Also, the tracking of HugeTLB reservations is a bit more