From: Jens Axboe <axboe@kernel.dk>
To: fio@vger.kernel.org
Subject: Re: New tools and changes
Date: Sat, 27 Sep 2014 14:39:35 -0600 [thread overview]
Message-ID: <54272087.10907@kernel.dk> (raw)
In-Reply-To: <54271828.2040005@kernel.dk>
Hi,
I forgot to mention another handy change that went in recently - fio now
supports including files from job files. This should make it easier to
manage a test harness of fio files, since you can have more manageable
files with a global (or per-host, whatever) include fio that has options
for that particular instance. It's pretty simple to use, here's the
section that was added to the HOWTO to explain it:
-----------
When fio is utilized as a basis of any reasonably large test suite, it
might be desirable to share a set of standardized settings across
multiple job files. Instead of copy/pasting such settings, any section
may pull in an external .fio file with 'include filename' directive, as
in the following example:
; -- start job file including.fio --
[global]
filename=/tmp/test
filesize=1m
include glob-include.fio
[test]
rw=randread
bs=4k
time_based=1
runtime=10
include test-include.fio
; -- end job file including.fio --
; -- start job file glob-include.fio --
thread=1
group_reporting=1
; -- end job file glob-include.fio --
; -- start job file test-include.fio --
ioengine=libaio
iodepth=4
; -- end job file test-include.fio --
Settings pulled into a section apply to that section only (except global
section). Include directives may be nested in that any included file may
contain further include directive(s). Include files may not contain []
sections.
--------
This feature courtesy of Andrey Kuzmin <andrey.v.kuzmin@gmail.com> who
did all the work to make this feasible.
--
Jens Axboe
prev parent reply other threads:[~2014-09-27 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-27 20:03 New tools and changes Jens Axboe
2014-09-27 20:39 ` 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=54272087.10907@kernel.dk \
--to=axboe@kernel.dk \
--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