summaryrefslogtreecommitdiff
path: root/options.c
diff options
context:
space:
mode:
authorJens Axboe <jaxboe@fusionio.com>2010-06-15 14:25:36 +0200
committerJens Axboe <jaxboe@fusionio.com>2010-06-15 14:25:36 +0200
commit9e144189c6e000df8a797312e43a4913f3b83c9a (patch)
treeaf628528b40bf104ca8e1a527b1647adcb3a0ed5 /options.c
parent2faf9ec84cc329304bd0dcbf928184e11e550108 (diff)
downloadfio-9e144189c6e000df8a797312e43a4913f3b83c9a.tar.gz
Add some support for a verify backlog
Instead of writing everything and then verifying everything, allow a job to specify incremental verify stages. This can help reduce memory consumption of fio, since we don't have to store a huge number of verify entries to be processed when the write phase is complete. Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
Diffstat (limited to 'options.c')
-rw-r--r--options.c14
1 files changed, 14 insertions, 0 deletions
diff --git a/options.c b/options.c
index 2369191c..f470b453 100644
--- a/options.c
+++ b/options.c
@@ -1410,6 +1410,20 @@ static struct fio_option options[FIO_MAX_OPTS] = {
.help = "Number of async verifier threads to use",
.parent = "verify",
},
+ {
+ .name = "verify_backlog",
+ .type = FIO_OPT_STR_VAL,
+ .off1 = td_var_offset(verify_backlog),
+ .help = "Verify after this number of blocks are written",
+ .parent = "verify",
+ },
+ {
+ .name = "verify_backlog_batch",
+ .type = FIO_OPT_INT,
+ .off1 = td_var_offset(verify_batch),
+ .help = "Verify this number of IO blocks",
+ .parent = "verify_backlog",
+ },
#ifdef FIO_HAVE_CPU_AFFINITY
{
.name = "verify_async_cpus",