Lines Matching refs:mlock
47 * Those mapped into VM_LOCKED [mlock()ed] VMAs.
167 the page tables for the region as does, for example, mlock(), nor need it make
187 list at mlock() or mmap() time, vmscan will not encounter the folios until they
214 The unevictable folio list is also useful for mlock(), in addition to ramfs and
215 SYSV SHM. Note that mlock() is only available in CONFIG_MMU=y situations; in
260 (1) in the mlock()/mlock2()/mlockall() system call handlers;
286 mlock()/mlock2()/mlockall() System Call Handling
289 mlock(), mlock2() and mlockall() system call handlers proceed to mlock_fixup()
292 is used for both mlocking and munlocking a range of memory. A call to mlock()
319 mlock folio batch, to batch up the rest of the work to be done under lru_lock by
347 neither need nor want to mlock() these pages. But __mm_populate() includes
368 mlock_fixup() function as mlock(), mlock2() and mlockall() system calls are.
379 munlock_folio() uses the mlock pagevec to batch up work to be done
408 (including mlock where VM_LOCKED). The page table locks provide sufficient
439 If a user tries to mlock() part of a huge page, and no user mlock()s the
442 We cannot just split the page on partial mlock() as split_huge_page() can
459 In addition to the mlock(), mlock2() and mlockall() system calls, an application
462 mmap() + mlock() will fail if the range cannot be faulted in (e.g. because
469 in the newly mapped memory being mlocked. Before the unevictable/mlock
473 To mlock a range of memory under the unevictable/mlock infrastructure,
475 populate_vma_page_range() specifying the vma and the address range to mlock.
484 Before the unevictable/mlock changes, mlocking did not mark the pages in any
491 munlock_folio() uses the mlock pagevec to batch up work to be done