Lines Matching full:list

29 The Unevictable LRU facility adds an additional LRU list to track unevictable
43 The unevictable list addresses the following classes of unevictable pages:
55 The Unevictable Page List
58 The Unevictable LRU infrastructure consists of an additional, per-zone, LRU list
59 called the "unevictable" list and an associated page flag, PG_unevictable, to
60 indicate that the page is being managed on the unevictable list.
63 PG_active flag in that it indicates on which LRU list a page resides when
67 LRU list for a few reasons:
77      lists.  If we were to maintain pages elsewhere than on an LRU-like list,
83 The unevictable list does not differentiate between file-backed and anonymous,
87 The unevictable list benefits from the "arrayification" of the per-zone LRU
90 The unevictable list does not use the LRU pagevec mechanism. Rather,
91 unevictable pages are placed directly on the page's zone's unevictable list
93 the unevictable list when one task has the page isolated from the LRU and other
105 list as a result of the "arrayification" of the per-zone LRU lists (one per
107 and from the unevictable list.
110 not attempt to reclaim pages on the unevictable list.  This has a couple of
113  (1) Because the pages are "hidden" from reclaim on the unevictable list, the
174 list.  Instead, vmscan will do this if and when it encounters the pages during
178 the pages in the region and "rescue" them from the unevictable list if no other
180 the pages are also "rescued" from the unevictable list in the process of
192 list at mlock() or mmap() time, vmscan will not encounter the pages until they
194 from the unevictable list.  However, there may be situations where we decide,
199 unevictable list for the zone being scanned.
207 To "cull" an unevictable page, vmscan simply puts the page back on the LRU list
211 unevictable state of a page that it places on the unevictable list.  If the
212 page has become unevictable, putback_lru_page() removes it from the list and
214 event and movement of pages onto the unevictable list should be rare, these
222 The unevictable page list is also useful for mlock(), in addition to ramfs and
235 In Nick's patch, he used one of the struct page LRU list link fields as a count
237 prevented the management of the pages on an LRU list, and thus mlocked pages
238 were not migratable as isolate_lru_page() could not find them, and the LRU list
241 Nick resolved this by putting mlocked pages back on the lru list before
256 A PG_mlocked page will be placed on the unevictable list when it is added to
276 mlocked pages become unlocked and rescued from the unevictable list when:
317 remaining on a normal LRU list without being PageMlocked().  Again, vmscan will
328 page from the LRU, as it is likely on the appropriate active or inactive list
331 is now mlocked and divert the page to the zone's unevictable list.  If
401 not be on an LRU list [more on these below].  However, the call to
433 list because of a race between munlock and migration, page migration uses the
450 A transparent huge page is represented by a single entry on an LRU list.
587 !page_evictable(page) - diverting these to the unevictable list.
590 set - otherwise they would be on the unevictable list and shrink_active_list
603      unevictable list in mlock_vma_page().
606 inactive lists to the appropriate zone's unevictable list.
609 after shrink_active_list() had moved them to the inactive list, or pages mapped
617 try_to_unmap().  shrink_page_list() will divert them to the unevictable list