Lines Matching full:s

9 Because VM is getting complex (one of reasons is memcg...), memcg's behavior
10 is complex. This is a document for memcg's internal behavior.
44 	  Called when a page's refcount goes down to 0.
47 	  Called when swp_entry's refcnt goes down to 0. A charge against swap
85 	    swp_entry's refcnt += 1.
87 	    swp_entry's refcnt += # of ptes.
90 	    swp_entry's refcnt -= 1.
94 	(e) zap_pte() is called and swp_entry's refcnt -=1 -> 0.
111 	The best way to understand shmem's page state transition is to read
117 	Shmem's page (just leaf page, not direct/indirect block) can be on
119 		- radix-tree of shmem's inode.
124 	It's charged when...
126 	- A new page is added to shmem's radix-tree.
137 	VM's control (means that it's handled under global pgdat->lru_lock).
138 	Almost all routines around memcg's LRU is called by global LRU's
142 	memcg's private LRU and call __isolate_lru_page() to extract a page
157 	When you do test to do racy case, it's good test to set memcg's limit
167 	Historically, memcg's shmem handling was poor and we saw some amount
261 	It's worth to be tested explicitly.
281 	Of course, tmpfs v.s. swapoff test should be tested, too.
286 	Out-of-memory caused by memcg's limit will kill tasks under
293 	It's not difficult to cause OOM under memcg as following.
355 	It's good idea to test root cgroup as well.