Home
last modified time | relevance | path

Searched refs:mlock_vma_page (Results 1 – 7 of 7) sorted by relevance

/linux-4.1.27/mm/
Dinternal.h258 extern void mlock_vma_page(struct page *page);
298 static inline void mlock_vma_page(struct page *page) { } in mlock_vma_page() function
Dmlock.c80 void mlock_vma_page(struct page *page) in mlock_vma_page() function
Dgup.c113 mlock_vma_page(page); in follow_page_pte()
Drmap.c1312 mlock_vma_page(page); in try_to_unmap_one()
Dksm.c1066 mlock_vma_page(kpage); in try_to_merge_one_page()
Dhuge_memory.c1245 mlock_vma_page(page); in follow_trans_huge_pmd()
/linux-4.1.27/Documentation/vm/
Dunevictable-lru.txt322 mark the pages as mlocked via mlock_vma_page().
333 mlock_vma_page(). If the mapping is gone, we just unlock the page and move on.
338 mlock_vma_page() will call TestSetPageMlocked() for each page returned by
342 statistics. If the page was already mlocked, mlock_vma_page() need do nothing
345 If the page was NOT already mlocked, mlock_vma_page() attempts to isolate the
347 at that time. If the isolate_lru_page() succeeds, mlock_vma_page() will put
350 mlock_vma_page() is unable to isolate the page from the LRU, vmscan will handle
408 flag using TestClearPageMlocked(). As with mlock_vma_page(),
541 mlock the page via mlock_vma_page() - we wouldn't have gotten to
592 for a locked VMA, try_to_unmap_cluster() calls mlock_vma_page() to
[all …]