On 02/13/2015 04:17 PM, Justin Eno (jeno) wrote:
For a (random) overwrite workload, 'size' amount of access doesn't correspond to each byte on the target having been touched, so setting size as the limit between write- and verify-phases doesn't really apply. The attached patch proposes to instead use io_limit as the limit if it's set. io_limit < size is already handled by subsequent logic. This patch just allows for io_limit > size.
Thanks Justin, applied. -- 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
