lkml.org 
[lkml]   [2018]   [Jun]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
Subject[QUESTION] About VM_LOCKONFAULT for file page
Date
Hi folks,


I did a quick test with mlock2 + VM_LOCKONFAULT flag. The test just does
an 1MB anonymous map and 1MB file map with VM_LOCKONFAULT respectively.
Then it tries to access one page of each mapping.


From /proc/meminfo, I can see 1 page marked mlocked from anonymous
mapping. But, the page from file mapping is *not* marked as mlocked.


I can see the do_anonymous_page() calls
lru_cache_add_active_or_unevictable() to set the page's PG_mlocked flag.
But, do_read_fault()/do_shared_fault()/do_cow_fault() don't do it, it
looks they just do it for COW page.


I'm a little bit confused. Does VM_LOCKONFAULT work for anonymous map
only? Or did I miss something? Any hint is appreciated.


Thanks,

Yang

\
 
 \ /
  Last update: 2018-06-04 20:56    [W:0.028 / U:0.024 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site