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

Attachment: io_limit.patch
Description: io_limit.patch

Reply via email to