Lines Matching refs:under

109         Each memcg has its own private LRU. Now, its handling is under global
110 	VM's control (means that it's handled under global zone->lru_lock).
112 	list management functions under zone->lru_lock().
127 	to be very small rather than GB. Many races found in the test under
129 	(Memory behavior under GB and Memory behavior under MB shows very
154 	under cpuset.
188 	run jobs under child_a and child_b
204 	and do task move, mkdir, rmdir etc...under this.
217 	Run malloc(100M) program under this. You'll see 60M of swaps.
227 	Out-of-memory caused by memcg's limit will kill tasks under
228 	the memcg. When hierarchy is used, a task under hierarchy
233 	It's not difficult to cause OOM under memcg as following.