From: Dmitry Monakhov <dmonakhov@openvz.org>
To: xfs@oss.sgi.com
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org,
dchinner@redhat.com, Dmitry Monakhov <dmonakhov@openvz.org>
Subject: [PATCH 0/8] xfstests: Stress tests improments v3
Date: Wed, 13 Feb 2013 12:49:55 +0400 [thread overview]
Message-ID: <1360745403-6373-1-git-send-email-dmonakhov@openvz.org> (raw)
This is third version of the patch series, previous version
can be found here: http://oss.sgi.com/archives/xfs/2012-09/msg00328.html
xfstests-add-fio-requirement-V2
xfstests-get-rid-of-hardcoded-sbin-mkfs
xfstest-add-configurable-load-factors
xfstest-allow-fsstress-to-use-load-factor-where-appr
run-check-to-common_rc
add-fallocate-truncate-vs-AIO-DIO-stress-test
add-fallocate-punch_hole-vs-AIO-DIO-stress-test
add-defragmentation-stress-tests-for-ext4
Changes since V2
Mostly code style cleanups accodring to Dave's comments
- add _scale_fsstress_args function
- move run_check function to common.rc
- Add more comments
- split combined e4defrag testcase in to disicated tescases.
next reply other threads:[~2013-02-13 8:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-13 8:49 Dmitry Monakhov [this message]
2013-02-13 8:49 ` [PATCH 1/8] xfstests: add fio requirement V2 Dmitry Monakhov
2013-02-13 8:49 ` [PATCH 2/8] xfstests: get rid of hardcoded /sbin/mkfs Dmitry Monakhov
2013-02-13 8:49 ` [PATCH 3/8] xfstest: add configurable load factors Dmitry Monakhov
2013-02-13 8:49 ` [PATCH 4/8] xfstest: allow fsstress to use load factor where appropriate Dmitry Monakhov
2013-02-13 8:50 ` [PATCH 5/8] xfstests: Move run_check to common.rc Dmitry Monakhov
2013-02-13 8:50 ` [PATCH 6/8] xfstests: add fallocate/truncate vs AIO/DIO stress test Dmitry Monakhov
2013-02-18 23:43 ` Dave Chinner
2013-02-13 8:50 ` [PATCH 7/8] xfstests: add fallocate/punch_hole " Dmitry Monakhov
2013-02-13 8:50 ` [PATCH 8/8] xfstests: add defragmentation stress tests for ext4 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=1360745403-6373-1-git-send-email-dmonakhov@openvz.org \
--to=dmonakhov@openvz.org \
--cc=dchinner@redhat.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 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).