Lines Matching full:under
65 Under below explanation, we assume CONFIG_SWAP=y.
138 each LRU handled under a single lru_lock for that memcg and node.
149 to be very small rather than GB. Many races found in the test under
152 (Memory behavior under GB and Memory behavior under MB shows very
181 under cpuset.::
223 run jobs under child_a and child_b
243 and do task move, mkdir, rmdir etc...under this.
261 Run malloc(100M) program under this. You'll see 60M of swaps.
275 Out-of-memory caused by memcg's limit will kill tasks under
276 the memcg. When hierarchy is used, a task under hierarchy
282 It's not difficult to cause OOM under memcg as following.