Lines Matching refs:when

174 for earlier. A file page will be accounted for as Page Cache when it's
178 An RSS page is unaccounted when it's fully unmapped. A PageCache page is
179 unaccounted when it's removed from radix-tree. Even if RSS pages are fully
201 But see section 8.2: when moving a task to another cgroup, its pages may
230 memory+swap. In other words, when we want to limit the usage of swap without
234 * What happens when a cgroup hits memory.memsw.limit_in_bytes
297 memory.kmem.usage_in_bytes, or in a separate counter when it makes sense.
303 to trigger slab reclaim when those limits are reached.
308 kernel memory, we prevent new processes from being created when the kernel
315 belong to the same memcg. This only fails to hold when a task is migrated to a
344     triggered for a cgroup when it hits K while staying below U, which makes
436 remain charged to it, the charge is dropped when the page is freed or
473   Also, note that when memory.kmem.limit_in_bytes is set the charges due to
537 	 file_mapped is accounted only when the memory cgroup is owner of page
565 value for efficient access. (Of course, when necessary, it's synchronized.)
644 no guarantees, but it does its best to make sure that when memory is
683 Note: Charges are moved only when you move mm->owner, in other words,
698 a page or a swap can be moved only when it is charged to the task's current
724 thresholds and gets notifications when it crosses.
732 Application will be notified through eventfd when memory usage crosses
743 delivery and gets notification when OOM happens.
751 The application will be notified through eventfd when OOM happens.
759 in memory cgroup's OOM-waitqueue when they request accountable memory.
819 Application will be notified through eventfd when memory pressure is at
845 3. Start reclamation in the background when the limit is