On Sat, Oct 15, 2016 at 11:59:22PM +0300, Amir Goldstein wrote: > So far so good, but then I looked closer at its sister test > generic/132, which is > an even more CPU intensive test, also of many small reads and writes > from few xfs_io runs. > This is not a 'quick' group test. > Here the runtime difference was significant 17sec without -M and 20sec > with -M flag. > > So without looking much closer into other non quick tests, I think > that perhaps the > best value option is to turn on -M flag for all the quick tests. > > What do you think? Sounds like a good idea, now how do we find out in the xfs_io helper if it's a quick test? -- To unsubscribe from this list: send the line "unsubscribe fstests" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
