From: Dave Chinner <david@fromorbit.com>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
hch@lst.de, xfs@oss.sgi.com
Subject: Re: [PATCH 3/6] xfstest: allow fsstress to use load factor where appropriate
Date: Thu, 27 Sep 2012 10:19:19 +1000 [thread overview]
Message-ID: <20120927001919.GD15236@dastard> (raw)
In-Reply-To: <1348496601-32637-3-git-send-email-dmonakhov@openvz.org>
On Mon, Sep 24, 2012 at 06:23:18PM +0400, Dmitry Monakhov wrote:
>
> Signed-off-by: Dmitry Monakhov <dmonakhov@openvz.org>
> ---
> 017 | 5 ++++-
> 068 | 4 ++--
> 070 | 4 +++-
> 076 | 5 ++++-
> 083 | 4 ++--
> 087 | 10 ++++++----
> 104 | 4 ++--
> 114 | 5 +++--
> 167 | 4 ++--
> 232 | 5 +++--
> 233 | 5 +++--
> 269 | 7 ++++---
> 270 | 7 ++++---
> 276 | 11 ++++++-----
> 14 files changed, 48 insertions(+), 32 deletions(-)
>
> diff --git a/017 b/017
> index 9ca0e72..8d35ee8 100755
> --- a/017
> +++ b/017
> @@ -67,7 +67,10 @@ echo "*** test"
> for l in 0 1 2 3 4
> do
> echo " *** test $l"
> - $FSSTRESS_PROG -d $SCRATCH_MNT -n 1000 $FSSTRESS_AVOID >>$seq.full
> + NUM=$((1000 * TIME_FACTOR))
$TIME_FACTOR, perhaps?
> + CPU=$((1 * LOAD_FACTOR))
> + $FSSTRESS_PROG -d $SCRATCH_MNT -n $NUM -p $CPU \
> + $FSSTRESS_AVOID >>$seq.full
I'd much prefer a wrapper around fsstress than have to code this
into every test. Something like:
run_fstress()
{
args=""
while [ $# -gt 0 ]; do
case "$1" in
-n) args="$args $1 $(($2 * $TIME_FACTOR))"; shift ;;
-p) args="$args $1 $(($2 * $LOAD_FACTOR))"; shift ;;
*) args="$args $1" ;;
esac
shift
done
$FSSTRESS_PROG $args
}
And so all you need to do is something like:
$ sed -i 's/\$FSSTRESS_PROG/run_fsstress/' [0-9][0-9][0-9]
To convert all tests that use fsstress to do this.
You might also want to do this for the tests that run dirstress as
well, and create a "stress" group so that you can run just
the stress tests easily....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2012-09-27 0:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 14:23 [PATCH 1/6] xfstests: add fio requirement V2 Dmitry Monakhov
2012-09-24 14:23 ` [PATCH 2/6] xfstest: add configurable load factors Dmitry Monakhov
2012-09-27 0:06 ` Dave Chinner
2012-09-24 14:23 ` [PATCH 3/6] xfstest: allow fsstress to use load factor where appropriate Dmitry Monakhov
2012-09-27 0:19 ` Dave Chinner [this message]
2012-09-24 14:23 ` [PATCH 4/6] add fallocate/truncate vs AIO/DIO stress test Dmitry Monakhov
2012-09-27 1:05 ` Dave Chinner
2012-09-24 14:23 ` [PATCH 5/6] add fallocate/punch_hole " Dmitry Monakhov
2012-09-27 1:07 ` Dave Chinner
2012-09-24 14:23 ` [PATCH 6/6] add defragmentation stress test for ext4 Dmitry Monakhov
2012-09-27 1:15 ` Dave Chinner
2012-09-27 0:19 ` [PATCH 1/6] xfstests: add fio requirement V2 Dave Chinner
[not found] <a>
2012-09-23 19:24 ` [PATCH 1/6] xfstest: add fio git submodule Dmitry Monakhov
2012-09-23 19:24 ` [PATCH 3/6] xfstest: allow fsstress to use load factor where appropriate 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=20120927001919.GD15236@dastard \
--to=david@fromorbit.com \
--cc=dmonakhov@openvz.org \
--cc=hch@lst.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).