On Wed, 24 May 2017, Laurent Dufour wrote:
A new configuration variable is introduced to activate the use of range lock instead of semaphore to protect per process memory layout. This range lock is replacing the use of a semaphore for mmap_sem. Currently only available for X86_64 and PPC64 architectures. By default this option is turned off and requires the EXPERT mode since it is not yet complete.
Just fyi I find this option quite useful for dev and debugging purposes, however it should not exist once any of this is seriously considered for merging. The reason being is that fundamentally such internals should not be exposed to configuration options. We either get it right for everybody, or we don't. I'm currently running lots of tests to see the overhead in real workloads on different boxes. While I hope that my artificial testing somewhat resembles some patterns, this will be the real deal. Thanks, Davidlohr -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
