Lines Matching refs:we

4       rewrite. It still contains a useful information so we are keeping it
14       When we mention a cgroup (cgroupfs's directory) with memory controller,
15       we call it "memory cgroup". When you see git-log and source code, you'll
17       In this document, we avoid using it.
100 that we handle both page cache and RSS together. Another request was raised
186 causing page fault. So, we avoid accounting at swap-in I/O.
190 Note: we just account pages-on-LRU because our purpose is to control amount
230 memory+swap. In other words, when we want to limit the usage of swap without
244 global VM. When a cgroup goes over its limit, we first try
254 NOTE: Reclaim does not work for the root cgroup, since we cannot set any
308 kernel memory, we prevent new processes from being created when the kernel
371 Since now we're in the 0 cgroup, we can alter the memory limit:
446 tasks have migrated away from it. (because we charge against pages, not
651 Soft limits can be setup by using the following commands (in this example we
656 If we want to change this to 1G, we can at any time use
685 Note: If we cannot find enough space for the task in the destination cgroup, we
686       try to make space by reclaiming memory. Task migration may fail if we
718   behavior to hold the mutex too long, so we may need some trick.
806 which disturbs the system and which is especially bad if we are low on