On 10/17/2016 11:22 PM, Christoph Hellwig wrote:
iThis series improves XFS discard support so that we don't stall the log commit thread and improve performance for workloads with lots of deletions. The first patch is a fix for a long-standing allocator issue when we have busy extents in the way of an allocation. Without the async discard support it was harder to hit, but it's basically been there since we added busy extent tracking and non-synchronous delete transactions. The second patch is the main async discard support, and the third one allows to batch up multiple extents into a single discard bio, which is a common occurance.
With these patches, is it reasonable to run with discard enabled, or is more work needed?
-- To unsubscribe from this list: send the line "unsubscribe linux-xfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
