On Mon, 2011-03-28 at 17:06 -0400, Christoph Hellwig wrote: > This series optimizes how XFS deals with busy extents. It starts to > track them exactly, and allows reuses where possible (metadata to metadata) > or else tries to avoid busy extents during allocations. This means > we don't have a single log force due to busy extents during either > xfstests, compilebench or postmark on my testsystem, which can easily > be tracked using the new tracepoints added in the last patch. > > This is a repost of the previous series and should address all review > comments. The discard support, which relies on the exact busy extent > tracking has been dropped temporarily until I can fix up some issues > that I found during testing. I've reviewed the series and it looks good to me. Unless someone else has comments that deserve some action I can take these in as-is. I'll wait for a bit though, to let the 2.6.39 merge window settle. I'm still curious what this (clipping busy blocks from consideration when allocating) will do to allocation patterns. Probably not much except in somewhat extreme conditions (when they already won't likely be that good). The "goodness" of allocation patterns are a bit hard to characterize anyway. -Alex _______________________________________________ xfs mailing list xfs@xxxxxxxxxxx http://oss.sgi.com/mailman/listinfo/xfs
