Hi all, I retested the ext4 barrier mitigation patchset against a base of 2.6.36-rc1 + Tejun's flush_fua tree + Christoph's patches to change FS barrier semantics, and came up with this new spreadsheet: http://bit.ly/bWpbsT Here are the previous 2.6.35 results for convenience: http://bit.ly/c22grd The machine configurations are the same as with the previous (2.6.35) spreadsheet. It appears to be the case that Tejun and Christoph's patches to change barrier use into simpler cache flushes generally improve the speed of the fsync-happy workload in buffered I/O mode ... if you have a bunch of spinning disks. Results for the SSD array (elm3c44) and the single disk systems (elm3c65/elm3c75) decreased slightly. For the case where direct I/O was used, the patchset improved the results in nearly all cases. The speed with barriers on is getting closer to the speed with barriers off, thankfully! Unfortunately, one thing that became /much/ less clear in these new results is the impact of the other patch sets that we've been working on to make ext4 smarter with regards to barrier/flush use. In most cases I don't really see the fsync-delay patch having much effect for directio, and it seems to have wild effects when buffered mode is used. Jan Kara's barrier generation patch still generally helps with directio loads. I've also concluded that my really old dirty-flag patchset from ages ago no longer has any effect. What does everyone else think of these results? --D -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
