| To: | Dmitry Monakhov <dmonakhov@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 01/10] xfstests: add fio requirement V2 |
| From: | Rich Johnston <rjohnston@xxxxxxx> |
| Date: | Fri, 1 Mar 2013 09:43:10 -0600 |
| Cc: | <xfs@xxxxxxxxxxx>, <linux-fsdevel@xxxxxxxxxxxxxxx>, <linux-ext4@xxxxxxxxxxxxxxx>, <dchinner@xxxxxxxxxx> |
| Delivered-to: | xfs@xxxxxxxxxxx |
| In-reply-to: | <1361356935-29153-2-git-send-email-dmonakhov@xxxxxxxxxx> |
| References: | <1361356935-29153-1-git-send-email-dmonakhov@xxxxxxxxxx> <1361356935-29153-2-git-send-email-dmonakhov@xxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 |
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@xxxxxxxxxx> Minor typos in the description, but looks good. Reviewed-by: Rich Johnston <rjohnston@xxxxxxx> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [PATCH v2] xfstests: use right defrag program path, Zheng Liu |
|---|---|
| Next by Date: | Re: [PATCH 02/10] xfstest: add configurable load factors, Rich Johnston |
| Previous by Thread: | [PATCH v2] xfstests: use right defrag program path, Zheng Liu |
| Next by Thread: | Re: [PATCH 02/10] xfstest: add configurable load factors, Rich Johnston |
| Indexes: | [Date] [Thread] [Top] [All Lists] |