From: Wu Fengguang <fengguang.wu@intel.com>
To: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>, Jan Kara <jack@suse.cz>,
Christoph Hellwig <hch@infradead.org>
Subject: writeback test scripts
Date: Tue, 15 Nov 2011 12:03:27 +0800 [thread overview]
Message-ID: <20111115040326.GA24233@localhost> (raw)
Hi,
I've uploaded the writeback test scripts to github:
(status: usable, ugly, a lot of rough edges)
git://github.com/fengguang/writeback-tests.git
https://github.com/fengguang/writeback-tests
The main features are
- automated dd/fio tests
- combinations of kernel/fs/fio job/nr_dd/dirty_thresh that is
hopefully complete enough to catch common performance regressions
- compare.rb for quickly evaluating performance and locate regressions
- detailed logs and graphs for analyzing regressions
To try it out,
1) copy all files to
/path/to/writeback-tests
2) basic configuration
cp fat-config.sh $(hostname)-config.sh
vi $(hostname)-config.sh
vi config.sh
Minimal configuration is to prepare at least one empty partition and
point DEVICES to it, create one empty mount point and point MNT to it.
3) add a hook at the end of rc.local:
/path/to/writeback-tests/main-loop.sh
main-loop.sh will test one case on each fresh boot. It will
automatically reboot the test box for each test cases until all done.
Each test run will save its log files to a unique directory
/path/to/writeback-tests/$(hostname)/<path1>/<path2>/
and if that directory already exists, the test case will be skipped.
We may further do a queue based job submission/execution system,
however this silly loop works good enough for me now :-)
Thanks,
Fengguang
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
reply other threads:[~2011-11-15 4:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20111115040326.GA24233@localhost \
--to=fengguang.wu@intel.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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).