Lines Matching full:under

65 Under below explanation, we assume CONFIG_MEM_RES_CTRL_SWAP=y.
136         Each memcg has its own private LRU. Now, its handling is under global
137 	VM's control (means that it's handled under global pgdat->lru_lock).
139 	list management functions under pgdat->lru_lock.
158 	to be very small rather than GB. Many races found in the test under
161 	(Memory behavior under GB and Memory behavior under MB shows very
190 	under cpuset.::
234 		run jobs under child_a and child_b
254 	and do task move, mkdir, rmdir etc...under this.
272 	Run malloc(100M) program under this. You'll see 60M of swaps.
286 	Out-of-memory caused by memcg's limit will kill tasks under
287 	the memcg. When hierarchy is used, a task under hierarchy
293 	It's not difficult to cause OOM under memcg as following.