Searched refs:mlock_count (Results 1 – 5 of 5) sorted by relevance
88 folio->mlock_count++; in __mlock_folio()95 folio->mlock_count = !!folio_test_mlocked(folio); in __mlock_folio()114 folio->mlock_count = !!folio_test_mlocked(folio); in __mlock_new_folio()135 if (folio->mlock_count) in __munlock_folio()136 folio->mlock_count--; in __munlock_folio()137 if (folio->mlock_count) in __munlock_folio()
196 folio->mlock_count = 0; in lru_add_fn()
2816 tail->mlock_count = 0; in lru_add_page_tail()
245 idea of keeping mlock_count in Unevictable LRU list link field was revived and322 __mlock_folio(). __mlock_folio() sets PG_unevictable, initializes mlock_count324 mlock_count in place of LRU threading). Or if the page was already PG_lru325 and PG_unevictable and PG_mlocked, it simply increments the mlock_count.328 it may have been temporarily isolated from LRU. In such cases the mlock_count383 folio's mlock_count, and when that reaches 0 it clears the mlocked flag389 those cases its mlock_count field is unusable and must be assumed to be 0: so495 folio's mlock_count, and when that reaches 0 it clears the mlocked flag501 those cases its mlock_count field is unusable and must be assumed to be 0: so522 and would not be counted out of mlock_count. In this rare case, a page may[all …]
96 unsigned int mlock_count; member336 unsigned int mlock_count; member