Lines Matching refs:munlock

189 have become evictable again (via munlock() for example) and have been "rescued"
274  (1) mapped in a range unlocked via the munlock()/munlockall() system calls;
292 an already VM_LOCKED VMA, or to munlock() a VMA that is not VM_LOCKED is
357 munlock(), munmap() or task exit.  Neither does mlock_fixup() account these
362 munlock()/munlockall() System Call Handling
365 The munlock() and munlockall() system calls are handled by the same functions -
371 ignored for munlock.
376 passing a flag to indicate that munlock() is being performed.
385 For munlock(), populate_vma_page_range() unlocks individual pages by calling
419 This has been discussed from the mlock/munlock perspective in the respective
429 list because of a race between munlock and migration, page migration uses the
501 munlock the pages if we're removing the last VM_LOCKED VMA that maps the pages.
505 To munlock a range of memory under the unevictable/mlock infrastructure, the
508 specifies the entire VMA range when munlock()ing during unmap of a region.
513 for the munlock case, calls __munlock_vma_pages_range() to walk the page table
546 munlock or munmap system calls, mm teardown (munlock_vma_pages_all), reclaim,
557 When munlock_vma_page() [see section :ref:`munlock()/munlockall() System Call
558 Handling <munlock_munlockall_handling>` above] tries to munlock a