Lines Matching full:fault

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
78 that, the application will get SIGBUS signal if it tries to fault in HugeTLB
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
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.
122 caused the reservation or fault has exited.
130 - The fault charges are charged to the parent HugeTLB cgroup (reparented),