Searched refs:LRU (Results 1 – 13 of 13) sorted by relevance
| /linux-2.6.39/Documentation/vm/ |
| D | unevictable-lru.txt | 2 UNEVICTABLE LRU INFRASTRUCTURE
9 (*) The Unevictable LRU
36 This document describes the Linux memory manager's "Unevictable LRU"
49 THE UNEVICTABLE LRU
52 The Unevictable LRU facility adds an additional LRU list to track unevictable
61 will spend a lot of time scanning the LRU lists looking for the small fraction
81 The Unevictable LRU infrastructure consists of an additional, per-zone, LRU list
86 PG_active flag in that it indicates on which LRU list a page resides when
89 The Unevictable LRU infrastructure maintains unevictable pages on an additional
90 LRU list for a few reasons:
[all …]
|
| D | pagemap.txt | 46 5. LRU
108 [LRU related page flags]
109 5. LRU page is in one of the LRU lists
110 6. ACTIVE page is in the active LRU list
111 18. UNEVICTABLE page is in the unevictable (non-)LRU list
112 It is somehow pinned and not a candidate for LRU page reclaims,
114 2. REFERENCED page has been referenced since last LRU list enqueue/requeue
|
| D | 00-INDEX | 38 - Unevictable LRU infrastructure
|
| D | page_migration | 62 1. Remove pages from the LRU.
86 already been removed from the LRU via isolate_lru_page() and the refcount
145 20. The new page is moved to the LRU and can be scanned by the swapper
|
| D | hwpoison.txt | 177 objects cannot be recovered, only LRU pages for now.
|
| /linux-2.6.39/Documentation/cgroups/ |
| D | memory.txt | 37 - private LRU and reclaim routine. (system's global LRU and private LRU
48 pages on LRU. To add more controls, we have to take care of performance.
147 updated. page_cgroup has its own LRU on cgroup.
153 Some pages which are never reclaimable and will not be on the global LRU
173 Note: we just account pages-on-LRU because our purpose is to control amount
174 of used pages; not-on-LRU pages tend to be out-of-control from VM view.
209 The global LRU(kswapd) can swap out arbitrary pages. Swap-out means
212 affecting global LRU, memory+swap limit is better than just limiting swap from
218 caches are dropped. But as mentioned above, global LRU can do swapout memory
224 Each cgroup maintains a per cgroup LRU which has the same structure as
[all …]
|
| D | memcg_test.txt | 207 (a) remove the page from LRU.
214 (g) pushback the page to LRU.
246 8. LRU
247 Each memcg has its own private LRU. Now, its handling is under global
249 Almost all routines around memcg's LRU is called by global LRU's
253 memcg's private LRU and call __isolate_lru_page() to extract a page
254 from LRU.
256 private LRU.)
|
| /linux-2.6.39/include/linux/ |
| D | page-flags.h | 203 PAGEFLAG(LRU, lru) __CLEARPAGEFLAG(LRU, lru)
|
| /linux-2.6.39/drivers/staging/spectra/ |
| D | flash.h | 102 u16 LRU; /* No. of the least recently used cache item */ member
|
| D | flash.c | 1339 Cache.LRU = bCurrentLRU; in FTL_Calculate_LRU()
1975 bNO = Cache.LRU; in FTL_Cache_Write()
2029 num = Cache.LRU; /* The LRU cache item will be overwritten */ in FTL_Cache_Read()
3845 cache_item = Cache.LRU; in GLOB_FTL_Page_Read()
3884 cache_blk = Cache.LRU; in GLOB_FTL_Page_Write()
|
| /linux-2.6.39/Documentation/trace/ |
| D | events-kmem.txt | 61 triggered. Broadly speaking, pages are taken off the LRU lock in bulk and
|
| /linux-2.6.39/Documentation/filesystems/caching/ |
| D | backend-api.txt | 435 to the LRU. Such pages must also be removed from the pages list and
|
| /linux-2.6.39/Documentation/filesystems/ |
| D | vfs.txt | 478 To achieve this functionality, pages need to be placed on an LRU with
1007 into an LRU list to be reclaimed on memory shortage.
|