All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	xfs@oss.sgi.com
Subject: Re: [PATCH 01/11] xfstests: add fio requirement V2
Date: Wed, 20 Feb 2013 12:14:17 +0400	[thread overview]
Message-ID: <87y5ej767a.fsf@openvz.org> (raw)
In-Reply-To: <20130220011854.GK10731@dastard>

On Wed, 20 Feb 2013 12:19:21 +1100, Dave Chinner <david@fromorbit.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@openvz.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@fromorbit.com

WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
	xfs@oss.sgi.com
Subject: Re: [PATCH 01/11] xfstests: add fio requirement V2
Date: Wed, 20 Feb 2013 12:14:17 +0400	[thread overview]
Message-ID: <87y5ej767a.fsf@openvz.org> (raw)
In-Reply-To: <20130220011854.GK10731@dastard>

On Wed, 20 Feb 2013 12:19:21 +1100, Dave Chinner <david@fromorbit.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@openvz.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@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2013-02-20  8:14 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19 11:37 [PATCH 01/11] xfstests: add fio requirement V2 Dmitry Monakhov
2013-02-19 11:37 ` [PATCH 02/11] xfstests: get rid of hardcoded /sbin/mkfs Dmitry Monakhov
2013-02-19 11:37   ` Dmitry Monakhov
2013-02-19 11:37 ` [PATCH 03/11] xfstest: add configurable load factors Dmitry Monakhov
2013-02-19 11:37   ` Dmitry Monakhov
2013-02-19 11:37 ` [PATCH 04/11] xfstests: hardcode fops for determinable fsstests runs Dmitry Monakhov
2013-02-19 11:37 ` [PATCH 05/11] xfstets: fsstress add replace file operation Dmitry Monakhov
2013-02-19 11:37   ` Dmitry Monakhov
2013-02-19 11:37 ` [PATCH 06/11] xfstest: allow fsstress to use load factor where appropriate Dmitry Monakhov
2013-02-19 11:37   ` Dmitry Monakhov
2013-02-19 11:37 ` [PATCH 07/11] xfstest: move run_check to common.rc Dmitry Monakhov
2013-02-19 11:37 ` [PATCH 08/11] xfstest: add fallocate/truncate vs AIO/DIO stress test Dmitry Monakhov
2013-02-19 11:37   ` Dmitry Monakhov
2013-02-19 11:37 ` [PATCH 09/11] xfstest: add fallocate/punch_hole " Dmitry Monakhov
2013-02-19 11:37   ` Dmitry Monakhov
2013-02-19 11:37 ` [PATCH 10/11] xfstest: add defragmentation stress tests for ext4 Dmitry Monakhov
2013-02-19 11:37   ` Dmitry Monakhov
2013-02-19 11:37 ` [PATCH 11/11] xfstests: add disk failure simulation test Dmitry Monakhov
2013-02-19 11:37   ` Dmitry Monakhov
2013-02-20  1:19 ` [PATCH 01/11] xfstests: add fio requirement V2 Dave Chinner
2013-02-20  1:19   ` Dave Chinner
2013-02-20  8:14   ` Dmitry Monakhov [this message]
2013-02-20  8:14     ` Dmitry Monakhov

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=87y5ej767a.fsf@openvz.org \
    --to=dmonakhov@openvz.org \
    --cc=david@fromorbit.com \
    --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.