Lines Matching refs:munlock

23      - munlock()/munlockall() system call handling.
210 have become evictable again (via munlock() for example) and have been "rescued"
296  (1) mapped in a range unlocked via the munlock()/munlockall() system calls;
314 an already VM_LOCKED VMA, or to munlock() a VMA that is not VM_LOCKED is
379 munlock(), munmap() or task exit.  Neither does mlock_fixup() account these
383 munlock()/munlockall() SYSTEM CALL HANDLING
386 The munlock() and munlockall() system calls are handled by the same functions -
392 ignored for munlock.
397 passing a flag to indicate that munlock() is being performed.
406 For munlock(), populate_vma_page_range() unlocks individual pages by calling
440 This has been discussed from the mlock/munlock perspective in the respective
450 list because of a race between munlock and migration, page migration uses the
495 munlock the pages if we're removing the last VM_LOCKED VMA that maps the pages.
499 To munlock a range of memory under the unevictable/mlock infrastructure, the
502 specifies the entire VMA range when munlock()ing during unmap of a region.
507 for the munlock case, calls __munlock_vma_pages_range() to walk the page table
613 When munlock_vma_page() [see section "munlock()/munlockall() System Call
614 Handling" above] tries to munlock a page, it needs to determine whether or not