unevictable-lru.rst - OpenGrok cross reference for /linux/Documentation/vm/unevictable-lru.rst

Lines Matching refs:mlock
49  * Those mapped into VM_LOCKED [mlock()ed] VMAs.
166 the page tables for the region as does, for example, mlock(), nor need it make
186 list at mlock() or mmap() time, vmscan will not encounter the pages until they
216 The unevictable page list is also useful for mlock(), in addition to ramfs and
217 SYSV SHM.  Note that mlock() is only available in CONFIG_MMU=y situations; in
253  (1) in the mlock()/mlockall() system call handlers;
283 mlock()/mlockall() System Call Handling
286 Both [do\_]mlock() and [do\_]mlockall() system call handlers call mlock_fixup()
289 is used for both mlocking and munlocking a range of memory.  A call to mlock()
306 migrated out from under us, while we're trying to mlock it.  To detect this,
342    neither need nor want to mlock() these pages.  However, to preserve the
343    prior behavior of mlock() - before the unevictable/mlock changes -
364 do_mlock[all]() - as the mlock() and mlockall() system calls with the unlock vs
373 populate_vma_page_range() - the same function used to mlock a VMA range -
417 This has been discussed from the mlock/munlock perspective in the respective
448 If a user tries to mlock() part of a huge page, we want the rest of the
451 We cannot just split the page on partial mlock() as split_huge_page() can
466 In addition the mlock()/mlockall() system calls, an application can request
468 call. There is one important and subtle difference here, though. mmap() + mlock()
476 in the newly mapped memory being mlocked.  Before the unevictable/mlock
480 To mlock a range of memory under the unevictable/mlock infrastructure, the
482 populate_vma_page_range() specifying the vma and the address range to mlock.
500 Before the unevictable/mlock changes, mlocking did not mark the pages in any
503 To munlock a range of memory under the unevictable/mlock infrastructure, the
538 VMA, it will then mlock the page via mlock_vma_page() instead of unmapping it,
543 to the page lock, and the rmap lock): to serialize against concurrent mlock or
555 page.  For this purpose, the unevictable/mlock infrastructure