Re: [PATCH 1/2] mmap.2: clarify MAP_LOCKED semantic

From
Peter Zijlstra <peterz@infradead.org>
Date
2016-05-11 11:18:12
Also in
linux-mm, lkml
Reply to
Peter Zijlstra, 2016-05-11

On 05/11/2016 01:07 PM, Peter Zijlstra wrote:
On 05/13/2015 04:38 PM, Michal Hocko wrote:
quoted
This patch makes the semantic of MAP_LOCKED explicit and suggest using
mmap + mlock as the only way to guarantee no later major page faults.
URGH, this really blows chunks. It basically means MAP_LOCKED is pointless cruft and we might as well remove it.

Why not fix it proper?
OK; after having been pointed at this discussion, it seems I reacted rather
too hasty in that I didn't read all the previous threads.

From that it appears fixing this proper is indeed rather hard, and we should
indeed consider MAP_LOCKED broken. At which point I would've worded the
manpage update stronger, but alas.

Sorry for the noise.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
Thread (14 messages) 14 messages, 7 authors, last reply 2016-05-11
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help