Lines Matching refs:into

71  (*) Those mapped into SHM_LOCK'd shared memory regions.
73  (*) Those mapped into VM_LOCKED [mlock()ed] VMAs.
143      the control group may not fit into the available memory.  This can cause
202 faulted into a VM_LOCKED vma, or found in a vma being VM_LOCKED.
218 There may be situations where a page is mapped into a VM_LOCKED VMA, but the
269 mlocked pages - pages mapped into a VM_LOCKED VMA - are a class of unevictable
326 do end up getting faulted into this VM_LOCKED VMA, we'll handle them in the
365 2) VMAs mapping hugetlbfs page are already effectively pinned into memory.  We
487 and pages allocated into that region.
516 Pages can, of course, be mapped into multiple VMAs.  Some of these VMAs may
517 have VM_LOCKED flag set.  It is possible for a page mapped into one or more
537      the page is mapped into a VM_LOCKED VMA, the scan stops.
633 For file pages mapped into non-linear VMAs, the try_to_munlock() logic works
640 reverse map to determine that a page is NOT mapped into any VM_LOCKED VMA.
670  (4) Pages mapped into multiple VM_LOCKED VMAs, but try_to_munlock() couldn't
680 into VM_LOCKED VMAs that munlock_vma_page() couldn't isolate from the LRU to
685 encounter for similar reason to shrink_inactive_list().  Pages mapped into