> The solution presented is not pretty. It creates a stream of leases, one > for each get_user_pages() invocation, and polls page reference counts > until DMA stops. We're missing a reliable way to not only trap the > DMA-idle event, but also block new references being taken on pages while > truncate is allowed to progress. "[PATCH v3 12/13] dax: handle truncate of > dma-busy pages" presents other options considered, and notes that this > solution can only be viewed as a stop-gap. I'd like to brainstorm how we can do something better. How about: If we hit a page with an elevated refcount in truncate / hole puch etc for a DAX file system we do not free the blocks in the file system, but add it to the extent busy list. We mark the page as delayed free (e.g. page flag?) so that when it finally hits refcount zero we call back into the file system to remove it from the busy list. -- 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>
