[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87y5ej767a.fsf@openvz.org>
Date: Wed, 20 Feb 2013 12:14:17 +0400
From: Dmitry Monakhov <dmonakhov@...nvz.org>
To: Dave Chinner <david@...morbit.com>
Cc: linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
xfs@....sgi.com
Subject: Re: [PATCH 01/11] xfstests: add fio requirement V2
On Wed, 20 Feb 2013 12:19:21 +1100, Dave Chinner <david@...morbit.com> wrote:
> On Tue, Feb 19, 2013 at 03:37:13PM +0400, 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@...nvz.org>
>
> Hi Dimitry,
>
> Can you rebase this series on top of a current xfstests tree? It
Ohhh. I use git://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git
> doesn't apply without conflicts or trying to land on top of existing
> files, so that makes it hard to actually test and do a final review
> on....
Will do ASAP.
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@...morbit.com
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists