linux-kernel - writeback test scripts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20111115040326.GA24233@localhost>
Date:	Tue, 15 Nov 2011 12:03:27 +0800
From:	Wu Fengguang <fengguang.wu@...el.com>
To:	"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>
Cc:	Linux Memory Management List <linux-mm@...ck.org>,
	LKML <linux-kernel@...r.kernel.org>, Jan Kara <jack@...e.cz>,
	Christoph Hellwig <hch@...radead.org>
Subject: writeback test scripts

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 from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/