On Sun, Oct 09, 2016 at 12:00:31PM -0700, Joel Fernandes wrote: > Ok. So I'll submit a patch with mutex for purge_lock and use > cond_resched_lock for the vmap_area_lock as you suggested. I'll also > drop the lazy_max_pages to 8MB as Andi suggested to reduce the lock > hold time. Let me know if you have any objections. The downside of using a mutex here though, is that we may be called from contexts that cannot sleep (alloc_vmap_area), or reschedule for that matter! If we change the notion of purged, we can forgo the mutex in favour of spinning on the direct reclaim path. That just leaves the complication of whether to use cond_resched_lock() or a lock around the individual __free_vmap_area(). -Chris -- Chris Wilson, Intel Open Source Technology Centre -- 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>