All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Srinivasa Chamarthy <chamarthy.raju@gmail.com>,
	Matthew Eaton <m.eaton82@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: achieving a workload to get specific unique duplicate blocks
Date: Thu, 07 May 2015 08:27:54 -0600	[thread overview]
Message-ID: <554B766A.2090703@kernel.dk> (raw)
In-Reply-To: <CABtFm2VhjHURUMHfB=iPoXZfa+_m8xm9qpBCQmv=2UB+Rd-BYA@mail.gmail.com>

On 05/06/2015 09:58 PM, Srinivasa Chamarthy wrote:
> Thanks Eaton. One question thought. From the man page for refill_buffers:
>
> "If this option is given, fio will refill the IO buffers on every
> submit. The default is to only fill it at init time and reuse that
> data. Only makes sense if zero_buffers isn't specified, naturally. If
> data verification is enabled, refill_buffers is also automatically
> enabled."
>
> Every IO submitted will have a new pattern for repeated workloads?
> using refill_buffers, i seem to get same pattern repeatedly. Is that
> how it should be? i was under the impression that refill will use new
> pattern every time.
>
> # fio --filename=test_refill --readwrite=randwrite --size=1m
> --refill_buffers --bs=256k --norandommap --name=refill
> # for each in {0..3}; do dd if=test_refill bs=262144 count=1
> skip=$each 2>/dev/null | md5sum; done
> 86c3e47e173a58ad93470fd8db856f8c  -
> 6fe5ce86d04522889c99809d6d97cb94  -
> 9113ce00f3781861afc41aaf6da32428  -
> f0b575c40e9da23b524f585723cbea4e  -
>
> # fio --filename=test_refill --readwrite=randwrite --size=1m
> --refill_buffers --bs=256k --norandommap --name=refill
> # for each in {0..3}; do dd if=test_refill bs=262144 count=1
> skip=$each 2>/dev/null | md5sum; done
> 86c3e47e173a58ad93470fd8db856f8c  -
> 6fe5ce86d04522889c99809d6d97cb94  -
> 9113ce00f3781861afc41aaf6da32428  -
> f0b575c40e9da23b524f585723cbea4e  -

First of all, please stop top posting. It breaks the flow of conversations.

Secondly, this is expected behavior, and it's done to get identical 
behavior between runs. If you had longer runs, each buffer would be 
different. But if you did a new run after that, the sequence of buffers 
would be the same. Same thing happens with the offsets generated, the 
buffer lengths generated, etc.

If you want a truly different run everytime, you have a few options. One 
is to simply set randrepeat=0, then OS entropy will seed the random 
generators. Or you can use randseed= to set a specific seed, which would 
allow you to reproduce a specific run.


-- 
Jens Axboe



  parent reply	other threads:[~2015-05-07 14:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-25 13:03 achieving a workload to get specific unique duplicate blocks Srinivasa Chamarthy
2015-05-04 20:39 ` Jens Axboe
2015-05-05  2:23   ` Srinivasa Chamarthy
2015-05-07  2:19     ` Matthew Eaton
2015-05-07  3:58       ` Srinivasa Chamarthy
2015-05-07  6:32         ` Srinivasa Chamarthy
2015-05-07 14:27         ` Jens Axboe [this message]
2015-05-07 15:30           ` Srinivasa Chamarthy
2015-05-08  9:35             ` Srinivasa Chamarthy
2015-05-08  6:04           ` Ruvinsky, Konstantin
2015-05-08  6:10             ` Ruvinsky, Konstantin

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=554B766A.2090703@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=chamarthy.raju@gmail.com \
    --cc=fio@vger.kernel.org \
    --cc=m.eaton82@gmail.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.