Today, fio has two distinct phases of operation: workload and then verify. But there is this hack which is in-between those two: verify_backlog which makes things a lot more complicated. This hack was added to limit the amount of memory needed to track the IOs that needed to be verify. I'm going to argue "verify_each_loop" could do the same thing and keep fio internals simpler (strictly two phases). If the goal is to have longer running, well defined workloads that can be verified, then verifying after each iteration makes more sense. In other words, the jobs should define a workload limit (amount of IO or time) and then iterate that constraint as many times as they want to reach the duration they want. Thoughts? thanks, grant -- To unsubscribe from this list: send the line "unsubscribe fio" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
