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 18:29:33 +0100 [thread overview]
Message-ID: <20091104172932.GD8742@kernel.dk> (raw)
In-Reply-To: <66dfd3fe0911040912s377b8b0eqb81fa3cad3db2d2f@mail.gmail.com>
On Wed, Nov 04 2009, Radha Ramachandran wrote:
> Yes, iodepth=x works. I did not realise that I could use iodepth with
> sync engine as well.
Good, we should probably default iodepth to verify_async + 1, if a
higher number isn't given. And/or document that you probably want to do
this.
--
Jens Axboe
next prev parent reply other threads:[~2009-11-04 17:29 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 [this message]
2009-11-04 17:39 ` Radha Ramachandran
2009-11-04 17:41 ` Jens Axboe
2009-11-04 19:22 ` Jens Axboe
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=20091104172932.GD8742@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