From: Rich Johnston <rjohnston@sgi.com>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: <xfs@oss.sgi.com>, <linux-fsdevel@vger.kernel.org>,
<linux-ext4@vger.kernel.org>, <dchinner@redhat.com>
Subject: Re: [PATCH 01/10] xfstests: add fio requirement V2
Date: Fri, 1 Mar 2013 09:43:10 -0600 [thread overview]
Message-ID: <5130CC8E.6090406@sgi.com> (raw)
In-Reply-To: <1361356935-29153-2-git-send-email-dmonakhov@openvz.org>
On 02/20/2013 04:42 AM, Dmitry Monakhov wrote:
> FIO is very flexible io generator, I would call it IO swiss knife.
> Currently we have tonns of hardcoded application which reproduces
> some predefined scenario. This approach has obvious dissadvantages
> 1) Lack of flexability: one written it is hard to modify it in future
> 2) Code base is large, many routines written again and again
>
> At the same time add new fio based tast is just add simle INI file.
> This greatly simplify code review. I do beleve that some day we will
> replace most of hardcoded io binaries with fio.
>
> One who is planning to run $FIO_PROG should first check that system
> contains appropriate version which is able to handle jobfile
> for example: _require_fio 286-job.fio
>
> Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
Minor typos in the description, but looks good.
Reviewed-by: Rich Johnston <rjohnston@sgi.com>
WARNING: multiple messages have this Message-ID (diff)
From: Rich Johnston <rjohnston@sgi.com>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
dchinner@redhat.com, xfs@oss.sgi.com
Subject: Re: [PATCH 01/10] xfstests: add fio requirement V2
Date: Fri, 1 Mar 2013 09:43:10 -0600 [thread overview]
Message-ID: <5130CC8E.6090406@sgi.com> (raw)
In-Reply-To: <1361356935-29153-2-git-send-email-dmonakhov@openvz.org>
On 02/20/2013 04:42 AM, Dmitry Monakhov wrote:
> FIO is very flexible io generator, I would call it IO swiss knife.
> Currently we have tonns of hardcoded application which reproduces
> some predefined scenario. This approach has obvious dissadvantages
> 1) Lack of flexability: one written it is hard to modify it in future
> 2) Code base is large, many routines written again and again
>
> At the same time add new fio based tast is just add simle INI file.
> This greatly simplify code review. I do beleve that some day we will
> replace most of hardcoded io binaries with fio.
>
> One who is planning to run $FIO_PROG should first check that system
> contains appropriate version which is able to handle jobfile
> for example: _require_fio 286-job.fio
>
> Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
Minor typos in the description, but looks good.
Reviewed-by: Rich Johnston <rjohnston@sgi.com>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-03-01 15:43 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 10:42 [PATCH 00/10] xfstests: Stress tests improments v5 Dmitry Monakhov
2013-02-20 10:42 ` [PATCH 01/10] xfstests: add fio requirement V2 Dmitry Monakhov
2013-02-20 10:42 ` Dmitry Monakhov
2013-03-01 15:43 ` Rich Johnston [this message]
2013-03-01 15:43 ` Rich Johnston
2013-02-20 10:42 ` [PATCH 02/10] xfstest: add configurable load factors Dmitry Monakhov
2013-02-20 10:42 ` Dmitry Monakhov
2013-03-01 15:43 ` Rich Johnston
2013-02-20 10:42 ` [PATCH 03/10] xfstests: hardcode fops for determinable fsstests runs Dmitry Monakhov
2013-02-20 10:42 ` Dmitry Monakhov
2013-03-01 15:43 ` Rich Johnston
2013-03-01 15:43 ` Rich Johnston
2013-02-20 10:42 ` [PATCH 04/10] xfstets: fsstress add replace file operation Dmitry Monakhov
2013-03-01 15:43 ` Rich Johnston
2013-02-20 10:42 ` [PATCH 05/10] xfstest: allow fsstress to use load factor where appropriate Dmitry Monakhov
2013-02-20 10:42 ` Dmitry Monakhov
2013-03-01 15:43 ` Rich Johnston
2013-02-20 10:42 ` [PATCH 06/10] xfstest: move run_check to common.rc Dmitry Monakhov
2013-02-20 10:42 ` Dmitry Monakhov
2013-03-01 15:44 ` Rich Johnston
2013-02-20 10:42 ` [PATCH 07/10] xfstest: add fallocate/truncate vs AIO/DIO stress test Dmitry Monakhov
2013-02-20 10:42 ` Dmitry Monakhov
2013-03-01 17:49 ` Rich Johnston
2013-03-01 17:49 ` Rich Johnston
2013-02-20 10:42 ` [PATCH 08/10] xfstest: add fallocate/punch_hole " Dmitry Monakhov
2013-02-20 10:42 ` Dmitry Monakhov
2013-03-01 17:50 ` Rich Johnston
2013-03-01 17:50 ` Rich Johnston
2013-02-20 10:42 ` [PATCH 09/10] xfstest: add defragmentation stress tests for ext4 Dmitry Monakhov
2013-02-20 10:42 ` Dmitry Monakhov
2013-03-01 19:23 ` Rich Johnston
2013-03-01 19:23 ` Rich Johnston
2013-03-02 1:30 ` Dmitry Monakhov
2013-03-02 1:30 ` Dmitry Monakhov
2013-03-04 23:19 ` Rich Johnston
2013-03-03 16:43 ` Zheng Liu
2013-03-03 16:43 ` Zheng Liu
2013-03-03 17:23 ` Zheng Liu
2013-03-03 17:23 ` Zheng Liu
2013-02-20 10:42 ` [PATCH 10/10] xfstests: add disk failure simulation test Dmitry Monakhov
2013-02-20 10:42 ` Dmitry Monakhov
2013-03-01 20:11 ` Rich Johnston
2013-03-02 1:49 ` Dmitry Monakhov
2013-03-04 23:44 ` Rich Johnston
2013-02-25 15:45 ` [PATCH 00/10] xfstests: Stress tests improments v5 Theodore Ts'o
2013-02-25 15:45 ` Theodore Ts'o
2013-02-25 21:28 ` Ben Myers
2013-02-25 21:28 ` Ben Myers
2013-02-25 22:09 ` Dave Chinner
2013-02-25 22:09 ` Dave Chinner
2013-02-25 23:00 ` Ben Myers
2013-02-25 23:00 ` Ben Myers
2013-03-01 20:23 ` Rich Johnston
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=5130CC8E.6090406@sgi.com \
--to=rjohnston@sgi.com \
--cc=dchinner@redhat.com \
--cc=dmonakhov@openvz.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=xfs@oss.sgi.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.