All of lore.kernel.org
 help / color / mirror / Atom feed
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 08:35:26 +0100	[thread overview]
Message-ID: <20091104073525.GQ8742@kernel.dk> (raw)
In-Reply-To: <66dfd3fe0911031633s5bef0621g99b4164c2dd174d9@mail.gmail.com>

On Tue, Nov 03 2009, Radha Ramachandran wrote:
> Hi,
> I was trying to use the async_verify option. Looks like if we use this
> option for synchronous I/O, then it really doesnt do anything as after
> every I/O is completed, we still need the asynchronous verify thread
> to complete the verification and release the io_u so the main thread
> can allocate this io_u for the next I/O. So to remove this bottle neck
> I added a new option extra_buff_count. This takes an integer and the
> code will allocate that many more extra io_us. This way when the main
> thread has completed the I/O it will have extra io_u and buffers to
> issue more I/Os while the asynchronous verify threads do their job.
> This can be used with both synchronous and libaio contexts.

Does iodepth=x not work for that? If not, I suggest we fix that instead
of adding a new parameter for it.

-- 
Jens Axboe


  reply	other threads:[~2009-11-04  7:35 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 [this message]
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
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=20091104073525.GQ8742@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.