From: Jens Axboe <jens.axboe@oracle.com>
To: Radha Ramachandran <radha@google.com>
Cc: fio@vger.kernel.org
Subject: Re: Add extra_buff_count flag
Date: Wed, 4 Nov 2009 20:22:30 +0100 [thread overview]
Message-ID: <20091104192230.GI8742@kernel.dk> (raw)
In-Reply-To: <20091104174123.GG8742@kernel.dk>
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
next prev parent reply other threads:[~2009-11-04 19:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-04 0:33 Add extra_buff_count flag Radha Ramachandran
2009-11-04 7:35 ` Jens Axboe
2009-11-04 17:12 ` Radha Ramachandran
2009-11-04 17:29 ` Jens Axboe
2009-11-04 17:39 ` Radha Ramachandran
2009-11-04 17:41 ` Jens Axboe
2009-11-04 19:22 ` Jens Axboe [this message]
2009-11-04 19:31 ` Radha Ramachandran
2009-11-04 19:36 ` Jens Axboe
2009-11-04 20:01 ` Jens Axboe
2009-11-04 22:50 ` Radha Ramachandran
2009-11-05 7:32 ` Jens Axboe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091104192230.GI8742@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=fio@vger.kernel.org \
--cc=radha@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox