From: Jens Axboe <axboe@kernel.dk>
To: Alket Memushaj <amemushaj@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: filling buffers with data from block device
Date: Wed, 28 Aug 2013 11:04:17 -0600 [thread overview]
Message-ID: <521E2D91.80600@kernel.dk> (raw)
In-Reply-To: <CA+BkS8NTwrsKpDnPqzcEBZRtOeK8xtOT0ZqeemPH36bTXOdP8w@mail.gmail.com>
On 08/27/2013 05:15 PM, Alket Memushaj wrote:
> is it possible to have fio fill the I/O buffers with data from a block
> device? when testing systems with both deduplication and compression
> enabled, it would be easier to fill the buffers with existing data.
It would not be impossible. But if you look at how fio allocates and
uses it's IO buffers, then you would need to continually fill them
before use since it reuses the same amount of them (defined by iodepth *
jobs).
It might be more feasible to analyze the data contents, and then improve
fio to be able to express that more easily.
--
Jens Axboe
prev parent reply other threads:[~2013-08-28 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 23:15 filling buffers with data from block device Alket Memushaj
2013-08-28 17:04 ` 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=521E2D91.80600@kernel.dk \
--to=axboe@kernel.dk \
--cc=amemushaj@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox