From: Jens Axboe <axboe@kernel.dk>
To: Surendar Chandra <surendar@datrium.com>, fio@vger.kernel.org
Subject: Re: buffer_pattern usage question
Date: Fri, 22 Aug 2014 10:24:27 -0500 [thread overview]
Message-ID: <53F760AB.9060908@kernel.dk> (raw)
In-Reply-To: <3DB5F5EE-7D4F-487B-B757-BAD37D041DEB@datrium.com>
On 2014-08-21 20:01, Surendar Chandra wrote:
> Could you please help me with this setup
>
> filename=fio-data
> size=4k
> rw=write
> buffer_pattern="HELLO"
>
> The output still continues to be pseudo random. I even tried buffer_pattern=0xDEADBEEF and other params.
It's not going to take a string, it needs to be a decimal of hexidecimal
number. I added some code to error out if it fails parsing this now.
buffer_pattern=0xDEADBEEF should work, and does for me:
axboe@lenny:/home/axboe/git/fio $ hexdump fio-data
0000000 beef dead beef dead beef dead beef dead
*
0001000
--
Jens Axboe
next prev parent reply other threads:[~2014-08-22 15:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 1:01 buffer_pattern usage question Surendar Chandra
2014-08-22 15:24 ` Jens Axboe [this message]
2014-08-22 17:59 ` Ruvinsky, Konstantin
2014-08-22 18:41 ` Sitsofe Wheeler
2014-08-22 18:58 ` Ruvinsky, Konstantin
2014-08-22 19:04 ` 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=53F760AB.9060908@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=surendar@datrium.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox