On Wed, Nov 04 2009, Jens Axboe wrote:
> On Wed, Nov 04 2009, Radha Ramachandran wrote:
> > I would rather document it than add it by default in case it starts
> > hitting memory constraints because its allocating more memory buffers.
>
> Yes I agree, I usually don't like having one option implying changes for
> another either.
So the problem with documentation is that usually nobody reads it. This
is what the HOWTO/man page currently has:
verify_async=int Fio will normally verify IO inline from the submitting
thread. This option takes an integer describing how many
async offload threads to create for IO verification instead,
causing fio to offload the duty of verifying IO contents
to one or more separate threads. If using this offload
option, even sync IO engines can benefit from using an
iodepth setting higher than 1, as it allows them to have
IO in flight while verifies are running.
It's already documented...
--
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
