On 04/13/2015 08:19 PM, Christoph Hellwig wrote: > On Mon, Apr 13, 2015 at 02:11:56PM +0300, Yigal Korman wrote: >> mlock() > > DAX files always are in-memory so this just sounds like an oversight. > method.
Yes mlock on DAX can just return true, but mlock implies MAP_POPULATE. Which means "I would like to page-fault the all mmap range at mmap time so at access time I'm guarantied not to sleep". This is usually done for latency sensitive applications. But current code fails on MAP_POPULATE for DAX because it is only implemented for pages, and therefor mlock fails as well. One thing I do not understand. does mlock also protects against truncate? Thanks Boaz -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
