From: Jens Axboe <axboe@kernel.dk>
To: "Neto,
Antonio Jose Rodrigues" <Antonio.Jose.Rodrigues.Neto@netapp.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Capturing and Replaying with blktrace (but with compression and dedupable 0)
Date: Tue, 06 Jan 2015 12:07:15 -0700 [thread overview]
Message-ID: <54AC3263.9020302@kernel.dk> (raw)
In-Reply-To: <D0D07E67.8EC4%Antonio.Jose.Rodrigues.Neto@netapp.com>
On 01/05/2015 03:46 PM, Neto, Antonio Jose Rodrigues wrote:
> Hi All,
>
> This is neto from Brazil
>
> How are you?
>
> Quick question:
>
> Capturing specific workload from customer A with blktrace and I want to
> replay with fio on customer B.
>
> I do not know how the workload was generated by customer A (with a bunch
> of NULLs or zeroes) and I would like to replay on customer B with scramble
> buffers and 0% dedupable and 0% compression.
>
> I do not see why this should not work� But just to confirm if anyone
> already has tested it.
That should work.
--
Jens Axboe
prev parent reply other threads:[~2015-01-06 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-05 22:46 Capturing and Replaying with blktrace (but with compression and dedupable 0) Neto, Antonio Jose Rodrigues
2015-01-06 19:07 ` Jens Axboe [this message]
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=54AC3263.9020302@kernel.dk \
--to=axboe@kernel.dk \
--cc=Antonio.Jose.Rodrigues.Neto@netapp.com \
--cc=fio@vger.kernel.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 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.