Lines Matching refs:unevictable

14 infrastructure and the use of this to manage several types of "unevictable"
29 The Unevictable LRU facility adds an additional LRU list to track unevictable
43 The unevictable list addresses the following classes of unevictable pages:
52 unevictable, either by definition or by circumstance, in the future.
64 called the "unevictable" list and an associated page flag, PG_unevictable, to
65 indicate that the page is being managed on the unevictable list.
71 The Unevictable LRU infrastructure maintains unevictable pages as if they were
74  (1) We get to "treat unevictable pages just like we treat other pages in the
79  (2) We want to be able to migrate unevictable pages between nodes for memory
86 The unevictable list does not differentiate between file-backed and anonymous,
90 The unevictable list benefits from the "arrayification" of the per-node LRU
97 The unevictable LRU facility interacts with the memory control group [aka
101 The memory controller data structure automatically gets a per-node unevictable
104 and from the unevictable list.
107 not attempt to reclaim pages on the unevictable list.  This has a couple of
110  (1) Because the pages are "hidden" from reclaim on the unevictable list, the
115      are unevictable, the evictable portion of the working set of the tasks in
132 	Mark the address space as being completely unevictable.
141 	unevictable.
154      amount of unevictable memory marked by i915 driver is roughly the bounded
163 :ref:`Marking address spaces unevictable <mark_addr_space_unevict>`]
169 any special effort to push any pages in the SHM_LOCK'd area to the unevictable
174 the pages in the region and "rescue" them from the unevictable list if no other
175 condition is keeping them unevictable.  If an unevictable region is destroyed,
176 the pages are also "rescued" from the unevictable list in the process of
187 If unevictable pages are culled in the fault path, or moved to the unevictable
190 from the unevictable list.  However, there may be situations where we decide,
191 for the sake of expediency, to leave an unevictable page on one of the regular
195 unevictable list for the memory cgroup and node being scanned.
201 is culled to the unevictable list when it is released by the shrinker.
203 To "cull" an unevictable page, vmscan simply puts the page back on the LRU list
205 dropping the page lock.  Because the condition which makes the page unevictable
207 unevictable state of a page before placing it on the unevictable list.
213 The unevictable page list is also useful for mlock(), in addition to ramfs and
251 mlocked pages - pages mapped into a VM_LOCKED VMA - are a class of unevictable
256 A PG_mlocked page will be placed on the unevictable list when it is added to
272 mlocked pages become unlocked and rescued from the unevictable list when:
320 and moves the page to unevictable state ("the unevictable LRU", but with
328 rather than risk stranding a page indefinitely as unevictable, always err with
351    unevictable and are not managed on the LRU lists.  __mm_populate() includes
381 PageUnevictable, moving the page from unevictable state to inactive LRU.
384 "the unevictable LRU", or it may have been temporarily isolated from it.  In
397 of mlocked pages and other unevictable pages.  PG_mlocked is cleared from the
400 was unevictable because mlocked, PG_unevictable follows PG_mlocked; but if the
401 page was unevictable for other reasons, PG_unevictable is copied explicitly.
424 is to let unevictable pages be moved.  /proc/sys/vm/compact_unevictable_allowed
434 Therefore, we can only make unevictable an entire compound page, not
448 to the unevictable LRU and the rest can be reclaimed.
467 in the newly mapped memory being mlocked.  Before the unevictable/mlock
471 To mlock a range of memory under the unevictable/mlock infrastructure,
482 Before the unevictable/mlock changes, mlocking did not mark the pages in any
492 PageUnevictable, moving the page from unevictable state to inactive LRU.
495 "the unevictable LRU", or it may have been temporarily isolated from it.  In
527 vmscan's shrink_active_list() culls any obviously unevictable pages -
528 i.e. !page_evictable(page) pages - diverting those to the unevictable list.
529 However, shrink_active_list() only sees unevictable pages that made it onto the
531 set - otherwise they would be on the unevictable list and shrink_active_list()
534 Some examples of these unevictable pages on the LRU lists are:
547 unevictable pages found on the inactive lists to the appropriate memory cgroup
548 and node unevictable list.
553 to correct them.  Such pages are culled to the unevictable list when released