Blame view
Documentation/vm/unevictable-lru.txt
32.8 KB
c24b72018 mm: reformat the ... |
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 |
============================== UNEVICTABLE LRU INFRASTRUCTURE ============================== ======== CONTENTS ======== (*) The Unevictable LRU - The unevictable page list. - Memory control group interaction. - Marking address spaces unevictable. - Detecting Unevictable Pages. - vmscan's handling of unevictable pages. (*) mlock()'d pages. - History. - Basic management. - mlock()/mlockall() system call handling. - Filtering special vmas. - munlock()/munlockall() system call handling. - Migrating mlocked pages. - mmap(MAP_LOCKED) system call handling. - munmap()/exit()/exec() system call handling. - try_to_unmap(). - try_to_munlock() reverse map scan. - Page reclaim in shrink_*_list(). ============ INTRODUCTION ============ This document describes the Linux memory manager's "Unevictable LRU" infrastructure and the use of this to manage several types of "unevictable" pages. The document attempts to provide the overall rationale behind this mechanism and the rationale for some of the design decisions that drove the implementation. The latter design rationale is discussed in the context of an implementation description. Admittedly, one can obtain the implementation details - the "what does it do?" - by reading the code. One hopes that the descriptions below add value by provide the answer to "why does it do that?". =================== THE UNEVICTABLE LRU =================== The Unevictable LRU facility adds an additional LRU list to track unevictable pages and to hide these pages from vmscan. This mechanism is based on a patch by Larry Woodman of Red Hat to address several scalability problems with page |
fa07e7877 doc: unevictable ... |
55 |
reclaim in Linux. The problems have been observed at customer sites on large |
c24b72018 mm: reformat the ... |
56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 |
memory x86_64 systems. To illustrate this with an example, a non-NUMA x86_64 platform with 128GB of main memory will have over 32 million 4k pages in a single zone. When a large fraction of these pages are not evictable for any reason [see below], vmscan will spend a lot of time scanning the LRU lists looking for the small fraction of pages that are evictable. This can result in a situation where all CPUs are spending 100% of their time in vmscan for hours or days on end, with the system completely unresponsive. The unevictable list addresses the following classes of unevictable pages: (*) Those owned by ramfs. (*) Those mapped into SHM_LOCK'd shared memory regions. (*) Those mapped into VM_LOCKED [mlock()ed] VMAs. The infrastructure may also be able to handle other conditions that make pages |
fa07e7877 doc: unevictable ... |
75 |
unevictable, either by definition or by circumstance, in the future. |
c24b72018 mm: reformat the ... |
76 77 |
THE UNEVICTABLE PAGE LIST ------------------------- |
fa07e7877 doc: unevictable ... |
78 79 80 |
The Unevictable LRU infrastructure consists of an additional, per-zone, LRU list called the "unevictable" list and an associated page flag, PG_unevictable, to |
c24b72018 mm: reformat the ... |
81 82 83 84 |
indicate that the page is being managed on the unevictable list. The PG_unevictable flag is analogous to, and mutually exclusive with, the PG_active flag in that it indicates on which LRU list a page resides when |
e6e8dd505 doc: CONFIG_UNEVI... |
85 |
PG_lru is set. |
fa07e7877 doc: unevictable ... |
86 87 88 |
The Unevictable LRU infrastructure maintains unevictable pages on an additional LRU list for a few reasons: |
c24b72018 mm: reformat the ... |
89 90 91 92 93 94 95 96 97 98 99 100 |
(1) We get to "treat unevictable pages just like we treat other pages in the system - which means we get to use the same code to manipulate them, the same code to isolate them (for migrate, etc.), the same code to keep track of the statistics, etc..." [Rik van Riel] (2) We want to be able to migrate unevictable pages between nodes for memory defragmentation, workload management and memory hotplug. The linux kernel can only migrate pages that it can successfully isolate from the LRU lists. If we were to maintain pages elsewhere than on an LRU-like list, where they can be found by isolate_lru_page(), we would prevent their migration, unless we reworked migration code to find the unevictable pages itself. |
fa07e7877 doc: unevictable ... |
101 |
|
fa07e7877 doc: unevictable ... |
102 |
|
c24b72018 mm: reformat the ... |
103 104 105 |
The unevictable list does not differentiate between file-backed and anonymous, swap-backed pages. This differentiation is only important while the pages are, in fact, evictable. |
fa07e7877 doc: unevictable ... |
106 |
|
c24b72018 mm: reformat the ... |
107 108 |
The unevictable list benefits from the "arrayification" of the per-zone LRU lists and statistics originally proposed and posted by Christoph Lameter. |
fa07e7877 doc: unevictable ... |
109 |
|
c24b72018 mm: reformat the ... |
110 111 112 113 114 |
The unevictable list does not use the LRU pagevec mechanism. Rather, unevictable pages are placed directly on the page's zone's unevictable list under the zone lru_lock. This allows us to prevent the stranding of pages on the unevictable list when one task has the page isolated from the LRU and other tasks are changing the "evictability" state of the page. |
fa07e7877 doc: unevictable ... |
115 |
|
fa07e7877 doc: unevictable ... |
116 |
|
c24b72018 mm: reformat the ... |
117 118 |
MEMORY CONTROL GROUP INTERACTION -------------------------------- |
fa07e7877 doc: unevictable ... |
119 |
|
c24b72018 mm: reformat the ... |
120 121 122 123 124 125 126 127 |
The unevictable LRU facility interacts with the memory control group [aka memory controller; see Documentation/cgroups/memory.txt] by extending the lru_list enum. The memory controller data structure automatically gets a per-zone unevictable list as a result of the "arrayification" of the per-zone LRU lists (one per lru_list enum element). The memory controller tracks the movement of pages to and from the unevictable list. |
fa07e7877 doc: unevictable ... |
128 |
|
fa07e7877 doc: unevictable ... |
129 130 |
When a memory control group comes under memory pressure, the controller will not attempt to reclaim pages on the unevictable list. This has a couple of |
c24b72018 mm: reformat the ... |
131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 |
effects: (1) Because the pages are "hidden" from reclaim on the unevictable list, the reclaim process can be more efficient, dealing only with pages that have a chance of being reclaimed. (2) On the other hand, if too many of the pages charged to the control group are unevictable, the evictable portion of the working set of the tasks in the control group may not fit into the available memory. This can cause the control group to thrash or to OOM-kill tasks. MARKING ADDRESS SPACES UNEVICTABLE ---------------------------------- For facilities such as ramfs none of the pages attached to the address space may be evicted. To prevent eviction of any such pages, the AS_UNEVICTABLE address space flag is provided, and this can be manipulated by a filesystem using a number of wrapper functions: (*) void mapping_set_unevictable(struct address_space *mapping); Mark the address space as being completely unevictable. (*) void mapping_clear_unevictable(struct address_space *mapping); Mark the address space as being evictable. (*) int mapping_unevictable(struct address_space *mapping); Query the address space, and return true if it is completely unevictable. These are currently used in two places in the kernel: (1) By ramfs to mark the address spaces of its inodes when they are created, and this mark remains for the life of the inode. (2) By SYSV SHM to mark SHM_LOCK'd address spaces until SHM_UNLOCK is called. Note that SHM_LOCK is not required to page in the locked pages if they're swapped out; the application must touch the pages manually if it wants to ensure they're in memory. DETECTING UNEVICTABLE PAGES --------------------------- The function page_evictable() in vmscan.c determines whether a page is evictable or not using the query function outlined above [see section "Marking address spaces unevictable"] to check the AS_UNEVICTABLE flag. For address spaces that are so marked after being populated (as SHM regions might be), the lock action (eg: SHM_LOCK) can be lazy, and need not populate the page tables for the region as does, for example, mlock(), nor need it make any special effort to push any pages in the SHM_LOCK'd area to the unevictable list. Instead, vmscan will do this if and when it encounters the pages during a reclamation scan. On an unlock action (such as SHM_UNLOCK), the unlocker (eg: shmctl()) must scan the pages in the region and "rescue" them from the unevictable list if no other condition is keeping them unevictable. If an unevictable region is destroyed, the pages are also "rescued" from the unevictable list in the process of freeing them. page_evictable() also checks for mlocked pages by testing an additional page flag, PG_mlocked (as wrapped by PageMlocked()). If the page is NOT mlocked, and a non-NULL VMA is supplied, page_evictable() will check whether the VMA is |
fa07e7877 doc: unevictable ... |
199 200 201 |
VM_LOCKED via is_mlocked_vma(). is_mlocked_vma() will SetPageMlocked() and update the appropriate statistics if the vma is VM_LOCKED. This method allows efficient "culling" of pages in the fault path that are being faulted in to |
c24b72018 mm: reformat the ... |
202 |
VM_LOCKED VMAs. |
fa07e7877 doc: unevictable ... |
203 |
|
c24b72018 mm: reformat the ... |
204 205 |
VMSCAN'S HANDLING OF UNEVICTABLE PAGES -------------------------------------- |
fa07e7877 doc: unevictable ... |
206 207 |
If unevictable pages are culled in the fault path, or moved to the unevictable |
c24b72018 mm: reformat the ... |
208 209 210 211 212 213 214 215 216 217 218 |
list at mlock() or mmap() time, vmscan will not encounter the pages until they have become evictable again (via munlock() for example) and have been "rescued" from the unevictable list. However, there may be situations where we decide, for the sake of expediency, to leave a unevictable page on one of the regular active/inactive LRU lists for vmscan to deal with. vmscan checks for such pages in all of the shrink_{active|inactive|page}_list() functions and will "cull" such pages that it encounters: that is, it diverts those pages to the unevictable list for the zone being scanned. There may be situations where a page is mapped into a VM_LOCKED VMA, but the page is not marked as PG_mlocked. Such pages will make it all the way to |
fa07e7877 doc: unevictable ... |
219 |
shrink_page_list() where they will be detected when vmscan walks the reverse |
c24b72018 mm: reformat the ... |
220 221 |
map in try_to_unmap(). If try_to_unmap() returns SWAP_MLOCK, shrink_page_list() will cull the page at that point. |
fa07e7877 doc: unevictable ... |
222 |
|
c24b72018 mm: reformat the ... |
223 224 225 226 227 228 229 230 231 232 |
To "cull" an unevictable page, vmscan simply puts the page back on the LRU list using putback_lru_page() - the inverse operation to isolate_lru_page() - after dropping the page lock. Because the condition which makes the page unevictable may change once the page is unlocked, putback_lru_page() will recheck the unevictable state of a page that it places on the unevictable list. If the page has become unevictable, putback_lru_page() removes it from the list and retries, including the page_unevictable() test. Because such a race is a rare event and movement of pages onto the unevictable list should be rare, these extra evictabilty checks should not occur in the majority of calls to putback_lru_page(). |
fa07e7877 doc: unevictable ... |
233 |
|
c24b72018 mm: reformat the ... |
234 235 236 |
============= MLOCKED PAGES ============= |
fa07e7877 doc: unevictable ... |
237 |
|
c24b72018 mm: reformat the ... |
238 239 240 241 242 243 244 245 246 |
The unevictable page list is also useful for mlock(), in addition to ramfs and SYSV SHM. Note that mlock() is only available in CONFIG_MMU=y situations; in NOMMU situations, all mappings are effectively mlocked. HISTORY ------- The "Unevictable mlocked Pages" infrastructure is based on work originally |
fa07e7877 doc: unevictable ... |
247 |
posted by Nick Piggin in an RFC patch entitled "mm: mlocked pages off LRU". |
c24b72018 mm: reformat the ... |
248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 |
Nick posted his patch as an alternative to a patch posted by Christoph Lameter to achieve the same objective: hiding mlocked pages from vmscan. In Nick's patch, he used one of the struct page LRU list link fields as a count of VM_LOCKED VMAs that map the page. This use of the link field for a count prevented the management of the pages on an LRU list, and thus mlocked pages were not migratable as isolate_lru_page() could not find them, and the LRU list link field was not available to the migration subsystem. Nick resolved this by putting mlocked pages back on the lru list before attempting to isolate them, thus abandoning the count of VM_LOCKED VMAs. When Nick's patch was integrated with the Unevictable LRU work, the count was replaced by walking the reverse map to determine whether any VM_LOCKED VMAs mapped the page. More on this below. BASIC MANAGEMENT ---------------- mlocked pages - pages mapped into a VM_LOCKED VMA - are a class of unevictable pages. When such a page has been "noticed" by the memory management subsystem, the page is marked with the PG_mlocked flag. This can be manipulated using the PageMlocked() functions. A PG_mlocked page will be placed on the unevictable list when it is added to the LRU. Such pages can be "noticed" by memory management in several places: (1) in the mlock()/mlockall() system call handlers; (2) in the mmap() system call handler when mmapping a region with the MAP_LOCKED flag; (3) mmapping a region in a task that has called mlockall() with the MCL_FUTURE flag (4) in the fault path, if mlocked pages are "culled" in the fault path, and when a VM_LOCKED stack segment is expanded; or (5) as mentioned above, in vmscan:shrink_page_list() when attempting to reclaim a page in a VM_LOCKED VMA via try_to_unmap() all of which result in the VM_LOCKED flag being set for the VMA if it doesn't already have it set. mlocked pages become unlocked and rescued from the unevictable list when: (1) mapped in a range unlocked via the munlock()/munlockall() system calls; (2) munmap()'d out of the last VM_LOCKED VMA that maps the page, including unmapping at task exit; (3) when the page is truncated from the last VM_LOCKED VMA of an mmapped file; or (4) before a page is COW'd in a VM_LOCKED VMA. mlock()/mlockall() SYSTEM CALL HANDLING --------------------------------------- |
fa07e7877 doc: unevictable ... |
307 308 |
Both [do_]mlock() and [do_]mlockall() system call handlers call mlock_fixup() |
c24b72018 mm: reformat the ... |
309 |
for each VMA in the range specified by the call. In the case of mlockall(), |
fa07e7877 doc: unevictable ... |
310 |
this is the entire active address space of the task. Note that mlock_fixup() |
c24b72018 mm: reformat the ... |
311 312 313 314 315 316 317 318 319 320 321 322 323 324 |
is used for both mlocking and munlocking a range of memory. A call to mlock() an already VM_LOCKED VMA, or to munlock() a VMA that is not VM_LOCKED is treated as a no-op, and mlock_fixup() simply returns. If the VMA passes some filtering as described in "Filtering Special Vmas" below, mlock_fixup() will attempt to merge the VMA with its neighbors or split off a subset of the VMA if the range does not cover the entire VMA. Once the VMA has been merged or split or neither, mlock_fixup() will call __mlock_vma_pages_range() to fault in the pages via get_user_pages() and to mark the pages as mlocked via mlock_vma_page(). Note that the VMA being mlocked might be mapped with PROT_NONE. In this case, get_user_pages() will be unable to fault in the pages. That's okay. If pages do end up getting faulted into this VM_LOCKED VMA, we'll handle them in the |
fa07e7877 doc: unevictable ... |
325 326 327 |
fault path or in vmscan. Also note that a page returned by get_user_pages() could be truncated or |
c24b72018 mm: reformat the ... |
328 329 330 331 332 333 334 335 336 337 338 339 340 341 |
migrated out from under us, while we're trying to mlock it. To detect this, __mlock_vma_pages_range() checks page_mapping() after acquiring the page lock. If the page is still associated with its mapping, we'll go ahead and call mlock_vma_page(). If the mapping is gone, we just unlock the page and move on. In the worst case, this will result in a page mapped in a VM_LOCKED VMA remaining on a normal LRU list without being PageMlocked(). Again, vmscan will detect and cull such pages. mlock_vma_page() will call TestSetPageMlocked() for each page returned by get_user_pages(). We use TestSetPageMlocked() because the page might already be mlocked by another task/VMA and we don't want to do extra work. We especially do not want to count an mlocked page more than once in the statistics. If the page was already mlocked, mlock_vma_page() need do nothing more. |
fa07e7877 doc: unevictable ... |
342 343 344 |
If the page was NOT already mlocked, mlock_vma_page() attempts to isolate the page from the LRU, as it is likely on the appropriate active or inactive list |
c24b72018 mm: reformat the ... |
345 346 347 |
at that time. If the isolate_lru_page() succeeds, mlock_vma_page() will put back the page - by calling putback_lru_page() - which will notice that the page is now mlocked and divert the page to the zone's unevictable list. If |
fa07e7877 doc: unevictable ... |
348 |
mlock_vma_page() is unable to isolate the page from the LRU, vmscan will handle |
c24b72018 mm: reformat the ... |
349 |
it later if and when it attempts to reclaim the page. |
fa07e7877 doc: unevictable ... |
350 |
|
c24b72018 mm: reformat the ... |
351 352 |
FILTERING SPECIAL VMAS ---------------------- |
fa07e7877 doc: unevictable ... |
353 |
|
c24b72018 mm: reformat the ... |
354 |
mlock_fixup() filters several classes of "special" VMAs: |
fa07e7877 doc: unevictable ... |
355 |
|
c24b72018 mm: reformat the ... |
356 |
1) VMAs with VM_IO or VM_PFNMAP set are skipped entirely. The pages behind |
fa07e7877 doc: unevictable ... |
357 |
these mappings are inherently pinned, so we don't need to mark them as |
c24b72018 mm: reformat the ... |
358 359 360 361 362 363 364 365 366 367 368 369 |
mlocked. In any case, most of the pages have no struct page in which to so mark the page. Because of this, get_user_pages() will fail for these VMAs, so there is no sense in attempting to visit them. 2) VMAs mapping hugetlbfs page are already effectively pinned into memory. We neither need nor want to mlock() these pages. However, to preserve the prior behavior of mlock() - before the unevictable/mlock changes - mlock_fixup() will call make_pages_present() in the hugetlbfs VMA range to allocate the huge pages and populate the ptes. 3) VMAs with VM_DONTEXPAND or VM_RESERVED are generally userspace mappings of kernel pages, such as the VDSO page, relay channel pages, etc. These pages |
fa07e7877 doc: unevictable ... |
370 |
are inherently unevictable and are not managed on the LRU lists. |
c24b72018 mm: reformat the ... |
371 |
mlock_fixup() treats these VMAs the same as hugetlbfs VMAs. It calls |
fa07e7877 doc: unevictable ... |
372 |
make_pages_present() to populate the ptes. |
c24b72018 mm: reformat the ... |
373 |
Note that for all of these special VMAs, mlock_fixup() does not set the |
fa07e7877 doc: unevictable ... |
374 |
VM_LOCKED flag. Therefore, we won't have to deal with them later during |
c24b72018 mm: reformat the ... |
375 376 377 378 379 380 381 382 383 384 385 386 387 |
munlock(), munmap() or task exit. Neither does mlock_fixup() account these VMAs against the task's "locked_vm". munlock()/munlockall() SYSTEM CALL HANDLING ------------------------------------------- The munlock() and munlockall() system calls are handled by the same functions - do_mlock[all]() - as the mlock() and mlockall() system calls with the unlock vs lock operation indicated by an argument. So, these system calls are also handled by mlock_fixup(). Again, if called for an already munlocked VMA, mlock_fixup() simply returns. Because of the VMA filtering discussed above, VM_LOCKED will not be set in any "special" VMAs. So, these VMAs will be |
fa07e7877 doc: unevictable ... |
388 |
ignored for munlock. |
c24b72018 mm: reformat the ... |
389 390 391 |
If the VMA is VM_LOCKED, mlock_fixup() again attempts to merge or split off the specified range. The range is then munlocked via the function __mlock_vma_pages_range() - the same function used to mlock a VMA range - |
fa07e7877 doc: unevictable ... |
392 |
passing a flag to indicate that munlock() is being performed. |
c24b72018 mm: reformat the ... |
393 |
Because the VMA access protections could have been changed to PROT_NONE after |
63d6c5ad7 mm: remove try_to... |
394 |
faulting in and mlocking pages, get_user_pages() was unreliable for visiting |
c24b72018 mm: reformat the ... |
395 |
these pages for munlocking. Because we don't want to leave pages mlocked, |
fa07e7877 doc: unevictable ... |
396 |
get_user_pages() was enhanced to accept a flag to ignore the permissions when |
c24b72018 mm: reformat the ... |
397 398 |
fetching the pages - all of which should be resident as a result of previous mlocking. |
fa07e7877 doc: unevictable ... |
399 400 401 |
For munlock(), __mlock_vma_pages_range() unlocks individual pages by calling munlock_vma_page(). munlock_vma_page() unconditionally clears the PG_mlocked |
c24b72018 mm: reformat the ... |
402 403 404 405 406 407 408 409 410 |
flag using TestClearPageMlocked(). As with mlock_vma_page(), munlock_vma_page() use the Test*PageMlocked() function to handle the case where the page might have already been unlocked by another task. If the page was mlocked, munlock_vma_page() updates that zone statistics for the number of mlocked pages. Note, however, that at this point we haven't checked whether the page is mapped by other VM_LOCKED VMAs. We can't call try_to_munlock(), the function that walks the reverse map to check for other VM_LOCKED VMAs, without first isolating the page from the LRU. |
fa07e7877 doc: unevictable ... |
411 |
try_to_munlock() is a variant of try_to_unmap() and thus requires that the page |
c24b72018 mm: reformat the ... |
412 413 414 415 |
not be on an LRU list [more on these below]. However, the call to isolate_lru_page() could fail, in which case we couldn't try_to_munlock(). So, we go ahead and clear PG_mlocked up front, as this might be the only chance we have. If we can successfully isolate the page, we go ahead and |
fa07e7877 doc: unevictable ... |
416 |
try_to_munlock(), which will restore the PG_mlocked flag and update the zone |
c24b72018 mm: reformat the ... |
417 |
page statistics if it finds another VMA holding the page mlocked. If we fail |
fa07e7877 doc: unevictable ... |
418 |
to isolate the page, we'll have left a potentially mlocked page on the LRU. |
c24b72018 mm: reformat the ... |
419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 |
This is fine, because we'll catch it later if and if vmscan tries to reclaim the page. This should be relatively rare. MIGRATING MLOCKED PAGES ----------------------- A page that is being migrated has been isolated from the LRU lists and is held locked across unmapping of the page, updating the page's address space entry and copying the contents and state, until the page table entry has been replaced with an entry that refers to the new page. Linux supports migration of mlocked pages and other unevictable pages. This involves simply moving the PG_mlocked and PG_unevictable states from the old page to the new page. Note that page migration can race with mlocking or munlocking of the same page. This has been discussed from the mlock/munlock perspective in the respective sections above. Both processes (migration and m[un]locking) hold the page locked. This provides the first level of synchronization. Page migration zeros out the page_mapping of the old page before unlocking it, so m[un]lock can skip these pages by testing the page mapping under page lock. To complete page migration, we place the new and old pages back onto the LRU after dropping the page lock. The "unneeded" page - old page on success, new page on failure - will be freed when the reference count held by the migration process is released. To ensure that we don't strand pages on the unevictable list because of a race between munlock and migration, page migration uses the putback_lru_page() function to add migrated pages back to the LRU. mmap(MAP_LOCKED) SYSTEM CALL HANDLING ------------------------------------- |
fa07e7877 doc: unevictable ... |
450 451 |
In addition the the mlock()/mlockall() system calls, an application can request |
c24b72018 mm: reformat the ... |
452 |
that a region of memory be mlocked supplying the MAP_LOCKED flag to the mmap() |
fa07e7877 doc: unevictable ... |
453 454 |
call. Furthermore, any mmap() call or brk() call that expands the heap by a task that has previously called mlockall() with the MCL_FUTURE flag will result |
c24b72018 mm: reformat the ... |
455 456 457 |
in the newly mapped memory being mlocked. Before the unevictable/mlock changes, the kernel simply called make_pages_present() to allocate pages and populate the page table. |
fa07e7877 doc: unevictable ... |
458 459 460 461 |
To mlock a range of memory under the unevictable/mlock infrastructure, the mmap() handler and task address space expansion functions call mlock_vma_pages_range() specifying the vma and the address range to mlock. |
c24b72018 mm: reformat the ... |
462 463 464 465 |
mlock_vma_pages_range() filters VMAs like mlock_fixup(), as described above in "Filtering Special VMAs". It will clear the VM_LOCKED flag, which will have already been set by the caller, in filtered VMAs. Thus these VMA's need not be visited for munlock when the region is unmapped. |
fa07e7877 doc: unevictable ... |
466 |
|
c24b72018 mm: reformat the ... |
467 |
For "normal" VMAs, mlock_vma_pages_range() calls __mlock_vma_pages_range() to |
fa07e7877 doc: unevictable ... |
468 469 |
fault/allocate the pages and mlock them. Again, like mlock_fixup(), mlock_vma_pages_range() downgrades the mmap semaphore to read mode before |
c24b72018 mm: reformat the ... |
470 |
attempting to fault/allocate and mlock the pages and "upgrades" the semaphore |
fa07e7877 doc: unevictable ... |
471 |
back to write mode before returning. |
c24b72018 mm: reformat the ... |
472 473 |
The callers of mlock_vma_pages_range() will have already added the memory range to be mlocked to the task's "locked_vm". To account for filtered VMAs, |
fa07e7877 doc: unevictable ... |
474 |
mlock_vma_pages_range() returns the number of pages NOT mlocked. All of the |
c24b72018 mm: reformat the ... |
475 476 477 478 479 |
callers then subtract a non-negative return value from the task's locked_vm. A negative return value represent an error - for example, from get_user_pages() attempting to fault in a VMA with PROT_NONE access. In this case, we leave the memory range accounted as locked_vm, as the protections could be changed later and pages allocated into that region. |
fa07e7877 doc: unevictable ... |
480 |
|
c24b72018 mm: reformat the ... |
481 482 |
munmap()/exit()/exec() SYSTEM CALL HANDLING ------------------------------------------- |
fa07e7877 doc: unevictable ... |
483 484 485 |
When unmapping an mlocked region of memory, whether by an explicit call to munmap() or via an internal unmap from exit() or exec() processing, we must |
c24b72018 mm: reformat the ... |
486 |
munlock the pages if we're removing the last VM_LOCKED VMA that maps the pages. |
63d6c5ad7 mm: remove try_to... |
487 488 |
Before the unevictable/mlock changes, mlocking did not mark the pages in any way, so unmapping them required no processing. |
fa07e7877 doc: unevictable ... |
489 490 |
To munlock a range of memory under the unevictable/mlock infrastructure, the |
c24b72018 mm: reformat the ... |
491 |
munmap() handler and task address space call tear down function |
fa07e7877 doc: unevictable ... |
492 |
munlock_vma_pages_all(). The name reflects the observation that one always |
c24b72018 mm: reformat the ... |
493 494 |
specifies the entire VMA range when munlock()ing during unmap of a region. Because of the VMA filtering when mlocking() regions, only "normal" VMAs that |
fa07e7877 doc: unevictable ... |
495 |
actually contain mlocked pages will be passed to munlock_vma_pages_all(). |
c24b72018 mm: reformat the ... |
496 |
munlock_vma_pages_all() clears the VM_LOCKED VMA flag and, like mlock_fixup() |
fa07e7877 doc: unevictable ... |
497 |
for the munlock case, calls __munlock_vma_pages_range() to walk the page table |
c24b72018 mm: reformat the ... |
498 499 500 |
for the VMA's memory range and munlock_vma_page() each resident page mapped by the VMA. This effectively munlocks the page, only if this is the last VM_LOCKED VMA that maps the page. |
fa07e7877 doc: unevictable ... |
501 |
|
fa07e7877 doc: unevictable ... |
502 |
|
c24b72018 mm: reformat the ... |
503 504 |
try_to_unmap() -------------- |
fa07e7877 doc: unevictable ... |
505 |
|
c24b72018 mm: reformat the ... |
506 |
Pages can, of course, be mapped into multiple VMAs. Some of these VMAs may |
fa07e7877 doc: unevictable ... |
507 |
have VM_LOCKED flag set. It is possible for a page mapped into one or more |
c24b72018 mm: reformat the ... |
508 509 510 511 512 513 514 |
VM_LOCKED VMAs not to have the PG_mlocked flag set and therefore reside on one of the active or inactive LRU lists. This could happen if, for example, a task in the process of munlocking the page could not isolate the page from the LRU. As a result, vmscan/shrink_page_list() might encounter such a page as described in section "vmscan's handling of unevictable pages". To handle this situation, try_to_unmap() checks for VM_LOCKED VMAs while it is walking a page's reverse map. |
fa07e7877 doc: unevictable ... |
515 516 |
try_to_unmap() is always called, by either vmscan for reclaim or for page |
c24b72018 mm: reformat the ... |
517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 |
migration, with the argument page locked and isolated from the LRU. Separate functions handle anonymous and mapped file pages, as these types of pages have different reverse map mechanisms. (*) try_to_unmap_anon() To unmap anonymous pages, each VMA in the list anchored in the anon_vma must be visited - at least until a VM_LOCKED VMA is encountered. If the page is being unmapped for migration, VM_LOCKED VMAs do not stop the process because mlocked pages are migratable. However, for reclaim, if the page is mapped into a VM_LOCKED VMA, the scan stops. try_to_unmap_anon() attempts to acquire in read mode the mmap semphore of the mm_struct to which the VMA belongs. If this is successful, it will mlock the page via mlock_vma_page() - we wouldn't have gotten to try_to_unmap_anon() if the page were already mlocked - and will return SWAP_MLOCK, indicating that the page is unevictable. If the mmap semaphore cannot be acquired, we are not sure whether the page is really unevictable or not. In this case, try_to_unmap_anon() will return SWAP_AGAIN. (*) try_to_unmap_file() - linear mappings Unmapping of a mapped file page works the same as for anonymous mappings, except that the scan visits all VMAs that map the page's index/page offset in the page's mapping's reverse map priority search tree. It also visits each VMA in the page's mapping's non-linear list, if the list is non-empty. As for anonymous pages, on encountering a VM_LOCKED VMA for a mapped file page, try_to_unmap_file() will attempt to acquire the associated mm_struct's mmap semaphore to mlock the page, returning SWAP_MLOCK if this is successful, and SWAP_AGAIN, if not. (*) try_to_unmap_file() - non-linear mappings If a page's mapping contains a non-empty non-linear mapping VMA list, then try_to_un{map|lock}() must also visit each VMA in that list to determine whether the page is mapped in a VM_LOCKED VMA. Again, the scan must visit all VMAs in the non-linear list to ensure that the pages is not/should not be mlocked. If a VM_LOCKED VMA is found in the list, the scan could terminate. However, there is no easy way to determine whether the page is actually mapped in a given VMA - either for unmapping or testing whether the VM_LOCKED VMA actually pins the page. try_to_unmap_file() handles non-linear mappings by scanning a certain number of pages - a "cluster" - in each non-linear VMA associated with the page's mapping, for each file mapped page that vmscan tries to unmap. If this happens to unmap the page we're trying to unmap, try_to_unmap() will notice this on return (page_mapcount(page) will be 0) and return SWAP_SUCCESS. Otherwise, it will return SWAP_AGAIN, causing vmscan to recirculate this page. We take advantage of the cluster scan in try_to_unmap_cluster() as follows: For each non-linear VMA, try_to_unmap_cluster() attempts to acquire the mmap semaphore of the associated mm_struct for read without blocking. If this attempt is successful and the VMA is VM_LOCKED, try_to_unmap_cluster() will retain the mmap semaphore for the scan; otherwise it drops it here. Then, for each page in the cluster, if we're holding the mmap semaphore for a locked VMA, try_to_unmap_cluster() calls mlock_vma_page() to mlock the page. This call is a no-op if the page is already locked, but will mlock any pages in the non-linear mapping that happen to be unlocked. If one of the pages so mlocked is the page passed in to try_to_unmap(), try_to_unmap_cluster() will return SWAP_MLOCK, rather than the default SWAP_AGAIN. This will allow vmscan to cull the page, rather than recirculating it on the inactive list. Again, if try_to_unmap_cluster() cannot acquire the VMA's mmap sem, it returns SWAP_AGAIN, indicating that the page is mapped by a VM_LOCKED VMA, but couldn't be mlocked. try_to_munlock() REVERSE MAP SCAN --------------------------------- [!] TODO/FIXME: a better name might be page_mlocked() - analogous to the page_referenced() reverse map walker. When munlock_vma_page() [see section "munlock()/munlockall() System Call Handling" above] tries to munlock a page, it needs to determine whether or not the page is mapped by any VM_LOCKED VMA without actually attempting to unmap all PTEs from the page. For this purpose, the unevictable/mlock infrastructure introduced a variant of try_to_unmap() called try_to_munlock(). |
fa07e7877 doc: unevictable ... |
608 609 610 611 |
try_to_munlock() calls the same functions as try_to_unmap() for anonymous and mapped file pages with an additional argument specifing unlock versus unmap processing. Again, these functions walk the respective reverse maps looking |
c24b72018 mm: reformat the ... |
612 |
for VM_LOCKED VMAs. When such a VMA is found for anonymous pages and file |
fa07e7877 doc: unevictable ... |
613 614 615 |
pages mapped in linear VMAs, as in the try_to_unmap() case, the functions attempt to acquire the associated mmap semphore, mlock the page via mlock_vma_page() and return SWAP_MLOCK. This effectively undoes the |
63d6c5ad7 mm: remove try_to... |
616 |
pre-clearing of the page's PG_mlocked done by munlock_vma_page. |
fa07e7877 doc: unevictable ... |
617 |
|
c24b72018 mm: reformat the ... |
618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 |
If try_to_unmap() is unable to acquire a VM_LOCKED VMA's associated mmap semaphore, it will return SWAP_AGAIN. This will allow shrink_page_list() to recycle the page on the inactive list and hope that it has better luck with the page next time. For file pages mapped into non-linear VMAs, the try_to_munlock() logic works slightly differently. On encountering a VM_LOCKED non-linear VMA that might map the page, try_to_munlock() returns SWAP_AGAIN without actually mlocking the page. munlock_vma_page() will just leave the page unlocked and let vmscan deal with it - the usual fallback position. Note that try_to_munlock()'s reverse map walk must visit every VMA in a page's reverse map to determine that a page is NOT mapped into any VM_LOCKED VMA. However, the scan can terminate when it encounters a VM_LOCKED VMA and can successfully acquire the VMA's mmap semphore for read and mlock the page. Although try_to_munlock() might be called a great many times when munlocking a large region or tearing down a large address space that has been mlocked via mlockall(), overall this is a fairly rare event. PAGE RECLAIM IN shrink_*_list() ------------------------------- shrink_active_list() culls any obviously unevictable pages - i.e. !page_evictable(page, NULL) - diverting these to the unevictable list. However, shrink_active_list() only sees unevictable pages that made it onto the active/inactive lru lists. Note that these pages do not have PageUnevictable set - otherwise they would be on the unevictable list and shrink_active_list would never see them. |
fa07e7877 doc: unevictable ... |
647 648 |
Some examples of these unevictable pages on the LRU lists are: |
c24b72018 mm: reformat the ... |
649 650 651 652 653 654 |
(1) ramfs pages that have been placed on the LRU lists when first allocated. (2) SHM_LOCK'd shared memory pages. shmctl(SHM_LOCK) does not attempt to allocate or fault in the pages in the shared memory region. This happens when an application accesses the page the first time after SHM_LOCK'ing the segment. |
fa07e7877 doc: unevictable ... |
655 |
|
c24b72018 mm: reformat the ... |
656 657 |
(3) mlocked pages that could not be isolated from the LRU and moved to the unevictable list in mlock_vma_page(). |
fa07e7877 doc: unevictable ... |
658 |
|
c24b72018 mm: reformat the ... |
659 660 661 662 |
(4) Pages mapped into multiple VM_LOCKED VMAs, but try_to_munlock() couldn't acquire the VMA's mmap semaphore to test the flags and set PageMlocked. munlock_vma_page() was forced to let the page back on to the normal LRU list for vmscan to handle. |
fa07e7877 doc: unevictable ... |
663 |
|
c24b72018 mm: reformat the ... |
664 665 |
shrink_inactive_list() also diverts any unevictable pages that it finds on the inactive lists to the appropriate zone's unevictable list. |
fa07e7877 doc: unevictable ... |
666 |
|
c24b72018 mm: reformat the ... |
667 668 669 670 671 |
shrink_inactive_list() should only see SHM_LOCK'd pages that became SHM_LOCK'd after shrink_active_list() had moved them to the inactive list, or pages mapped into VM_LOCKED VMAs that munlock_vma_page() couldn't isolate from the LRU to recheck via try_to_munlock(). shrink_inactive_list() won't notice the latter, but will pass on to shrink_page_list(). |
fa07e7877 doc: unevictable ... |
672 673 |
shrink_page_list() again culls obviously unevictable pages that it could |
63d6c5ad7 mm: remove try_to... |
674 |
encounter for similar reason to shrink_inactive_list(). Pages mapped into |
c24b72018 mm: reformat the ... |
675 |
VM_LOCKED VMAs but without PG_mlocked set will make it all the way to |
63d6c5ad7 mm: remove try_to... |
676 677 |
try_to_unmap(). shrink_page_list() will divert them to the unevictable list when try_to_unmap() returns SWAP_MLOCK, as discussed above. |