forked from Minki/linux
9b012a29a3
There is a very subtle difference between mmap()+mlock() vs mmap(MAP_LOCKED) semantic. The former one fails if the population of the area fails while the later one doesn't. This basically means that mmap(MAPLOCKED) areas might see major fault after mmap syscall returns which is not the case for mlock. mmap man page has already been altered but Documentation/vm/unevictable-lru.txt deserves a clarification as well. Signed-off-by: Michal Hocko <mhocko@suse.cz> Reported-by: David Rientjes <rientjes@google.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> |
||
|---|---|---|
| .. | ||
| .gitignore | ||
| 00-INDEX | ||
| active_mm.txt | ||
| balance | ||
| cleancache.txt | ||
| frontswap.txt | ||
| highmem.txt | ||
| hugetlbpage.txt | ||
| hwpoison.txt | ||
| ksm.txt | ||
| numa | ||
| numa_memory_policy.txt | ||
| overcommit-accounting | ||
| page_migration | ||
| page_owner.txt | ||
| pagemap.txt | ||
| remap_file_pages.txt | ||
| slub.txt | ||
| soft-dirty.txt | ||
| split_page_table_lock | ||
| transhuge.txt | ||
| unevictable-lru.txt | ||
| zsmalloc.txt | ||
| zswap.txt | ||