On Wed, Feb 05 2014, Grant Grundler wrote: > > It does - that's the log_io_piece() mechanism. The writer will generate > > on, and verify will read those and verify. We just have to ensure that > > it is correct in the way that it is logged. The alternative would be to > > rely purely on the generator rollback, and for that you would then need > > some specific notification on how far the reader could proceed, if async > > verify_backlog is used. > > Yes - I was referring to the "rely purely on generator rollback". > > Once log_io_piece() is called, the verify code assumes the IO is > complete...which isn't true if log_io_piece() is used to record "order > issued". Right, we'd need to ensure the state is accurately known to the verifier. -- Jens Axboe -- 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
