From mboxrd@z Thu Jan  1 00:00:00 1970
From: Pat LaVarre <p.lavarre@ieee.org>
Subject: Re: vfs whitebox test
Date: 25 Nov 2003 10:33:50 -0700
Sender: linux-fsdevel-owner@vger.kernel.org
Message-ID: <1069781630.2848.14.camel@patrh9>
References: <1069716562.4649.14.camel@patrh9>
	 <1069775182.6929.14.camel@patrh9>
	 <20031125090930.281f7864.rddunlap@osdl.org>
Mime-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Cc: linux-fsdevel@vger.kernel.org
Return-path: <linux-fsdevel-owner@vger.kernel.org>
Received: from email-out2.iomega.com ([147.178.1.83]:53225 "EHLO
	email.iomega.com") by vger.kernel.org with ESMTP id S262094AbTKYRe0
	(ORCPT <rfc822;linux-fsdevel@vger.kernel.org>);
	Tue, 25 Nov 2003 12:34:26 -0500
To: rddunlap@osdl.org
In-Reply-To: <20031125090930.281f7864.rddunlap@osdl.org>
List-Id: linux-fsdevel.vger.kernel.org

> ... ltp ... fsstress ...
> ... iozone ... Lots of file I/O, little VFS metadata activity.
> ... cruft ... fsx-linux in particular
> ... postmark ... many small files... more ... metadata ...

Guidance!  Thank you.  In particular, as I carry these links forward
hopefully now instead I will remember to say:

http://www.codemonkey.org.uk/cruft/fsx-linux.c

At first glance in fsx-linux.c I think I see command line "usage"
defined to produce open/ close/ read/ write/ lseek/ mmap/ munmap
sequences.

Pat LaVarre

P.S. Also thank you I picked up:

http://www.google.com/search?q=tiobench+sf.net
http://tiobench.sourceforge.net/
http://sourceforge.net/projects/tiobench/

self-described as: "portable, robust, fully-threaded I/O benchmark
program".