From: Jens Axboe <axboe@kernel.dk>
To: Matthew Eaton <m.eaton82@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: Possible bug when setting compression
Date: Fri, 14 Mar 2014 15:33:42 -0600 [thread overview]
Message-ID: <532375B6.1060208@kernel.dk> (raw)
In-Reply-To: <CAF+0mvmV4DYyGvG_ccENE5NqhB-wuQsqUVQD8LY0mvM-hTeXoA@mail.gmail.com>
On 03/14/2014 03:06 PM, Matthew Eaton wrote:
>> zero_buffers and buffer_compres_percentage=100 are essentially the same
>> thing, for both cases it writes buffers just fill of zeroes. So I'm not sure
>> what you were expecting here since you don't think it works as it should?
>>
>> If you have both zero_buffers and scramble set, then the result will be a
>> bit less compressible. The goal of scramble_buffers is to defeat basic
>> dedupe attempts. So even if you don't fully refill your buffers every time,
>> the blocks will be a bit different.
>>
>> --
>> Jens Axboe
>>
>>
>
> Hmm, I was assuming that scramble_buffers shouldn't have any effect
> since it's scrambling all zeros. Is scramble_buffers inserting random
> data even with zero_buffers set?
scramble_buffers tells fio to randomly insert some data in the buffer.
It's not a full overwrite or anything like that, just some basic garbage
for each 512b to prevent naive compression/dedupe.
--
Jens Axboe
next prev parent reply other threads:[~2014-03-14 21:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 15:52 Possible bug when setting compression Matthew Eaton
2014-03-14 18:26 ` Jens Axboe
2014-03-14 19:45 ` Matthew Eaton
2014-03-14 20:09 ` Jens Axboe
2014-03-14 20:23 ` Jens Axboe
2014-03-14 20:53 ` Matthew Eaton
2014-03-14 20:56 ` Jens Axboe
2014-03-14 21:06 ` Matthew Eaton
2014-03-14 21:33 ` Jens Axboe [this message]
2014-03-14 22:26 ` Matthew Eaton
2014-03-15 1:39 ` 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=532375B6.1060208@kernel.dk \
--to=axboe@kernel.dk \
--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.