From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from relay.sgi.com (relay1.corp.sgi.com [137.38.102.111]) by oss.sgi.com (Postfix) with ESMTP id 3DE4B7FBD for ; Fri, 1 Mar 2013 09:43:09 -0600 (CST) Message-ID: <5130CC8E.6090406@sgi.com> Date: Fri, 1 Mar 2013 09:43:10 -0600 From: Rich Johnston MIME-Version: 1.0 Subject: Re: [PATCH 01/10] xfstests: add fio requirement V2 References: <1361356935-29153-1-git-send-email-dmonakhov@openvz.org> <1361356935-29153-2-git-send-email-dmonakhov@openvz.org> In-Reply-To: <1361356935-29153-2-git-send-email-dmonakhov@openvz.org> List-Id: XFS Filesystem from SGI List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Errors-To: xfs-bounces@oss.sgi.com Sender: xfs-bounces@oss.sgi.com To: Dmitry Monakhov Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, dchinner@redhat.com, xfs@oss.sgi.com 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 Minor typos in the description, but looks good. Reviewed-by: Rich Johnston _______________________________________________ xfs mailing list xfs@oss.sgi.com http://oss.sgi.com/mailman/listinfo/xfs