Lines Matching refs:munlock

193 have become evictable again (via munlock() for example) and have been "rescued"
278  (1) mapped in a range unlocked via the munlock()/munlockall() system calls;
296 an already VM_LOCKED VMA, or to munlock() a VMA that is not VM_LOCKED is
361 munlock(), munmap() or task exit.  Neither does mlock_fixup() account these
366 munlock()/munlockall() System Call Handling
369 The munlock() and munlockall() system calls are handled by the same functions -
375 ignored for munlock.
380 passing a flag to indicate that munlock() is being performed.
389 For munlock(), populate_vma_page_range() unlocks individual pages by calling
423 This has been discussed from the mlock/munlock perspective in the respective
433 list because of a race between munlock and migration, page migration uses the
505 munlock the pages if we're removing the last VM_LOCKED VMA that maps the pages.
509 To munlock a range of memory under the unevictable/mlock infrastructure, the
512 specifies the entire VMA range when munlock()ing during unmap of a region.
517 for the munlock case, calls __munlock_vma_pages_range() to walk the page table
550 munlock or munmap system calls, mm teardown (munlock_vma_pages_all), reclaim,
561 When munlock_vma_page() [see section :ref:`munlock()/munlockall() System Call
562 Handling <munlock_munlockall_handling>` above] tries to munlock a