Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Taisuke Yamada <tai@rakugaki.org>
Cc: fio@vger.kernel.org
Subject: Re: [PATCH 1/2] Added replay_rebase option to run multi-threaded log replay on different disk sectors.
Date: Fri, 09 Sep 2011 10:37:34 +0200	[thread overview]
Message-ID: <4E69D04E.3090705@kernel.dk> (raw)
In-Reply-To: <4E69A048.6050509@rakugaki.org>

On 2011-09-09 07:12, Taisuke Yamada wrote:
> Hi.
> 
> I'm now trying to run multi-threaded log replay, and noticed
> all threads are accessing same sector on a disk. Of course,
> this is an expected behavior of "replay".
> 
> But since I also wanted to have each thread accessing different
> parts of the disk to increase a load, but still following the
> access pattern of the original, I added "replay_rebase" option to
> shift offset of IO request for each thread.
> 
> Althrough there's "1/2" in the subject, this patch is complete
> by itself. Next one (2/2) is related, but handles different issue.

Thanks, I can see this being handy. I can apply this, but I would much
prefer if you resend it with the proper updates to HOWTO and fio.1
adding the new option. Otherwise nobody is going to learn about it.

-- 
Jens Axboe


  reply	other threads:[~2011-09-09  8:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-09  5:12 [PATCH 1/2] Added replay_rebase option to run multi-threaded log replay on different disk sectors Taisuke Yamada
2011-09-09  8:37 ` Jens Axboe [this message]
2011-09-15  6:23   ` Taisuke Yamada
2011-09-15 11:10     ` Jens Axboe
2011-09-15 11:52       ` Taisuke Yamada
2011-09-15 11:14     ` Jens Axboe
2011-09-15 11:40       ` Taisuke Yamada
2011-09-15 11:42         ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2011-09-12  5:30 Taisuke Yamada

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=4E69D04E.3090705@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=tai@rakugaki.org \
    /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