From: Jens Axboe <jaxboe@fusionio.com>
To: majianpeng <majianpeng@gmail.com>
Cc: fio <fio@vger.kernel.org>
Subject: Re: The relation about size/filesize/nrfiles
Date: Thu, 10 Jan 2013 13:14:54 +0100 [thread overview]
Message-ID: <50EEB0BE.90909@fusionio.com> (raw)
In-Reply-To: <2013011020083650949610@gmail.com>
On 2013-01-10 13:08, majianpeng wrote:
> Hi all,
> I wanted to test some files.But i wanted to use size rather than nrfiles.The job file is:
> [global]
> rw=write
> directory=/media
> bs=64k
> size=500M
>
> [j1]
> filesize=256k
>
> But fio only created one file.If i used nrfiles,the size is ignored.
> So how to write which can do what i wanted?
If you just set size= and nrfiles=, then the file size will set according
to that. By default, each file will be size / nrfiles. You can influence
that with filesize=low:high.
The above wont work, fio will not calculate the number of files
needed to satisfy that job file (it could though, I'll take a patch!).
--
Jens Axboe
prev parent reply other threads:[~2013-01-10 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-10 12:08 The relation about size/filesize/nrfiles majianpeng
2013-01-10 12:14 ` 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=50EEB0BE.90909@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=fio@vger.kernel.org \
--cc=majianpeng@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox