All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pat LaVarre <p.lavarre@ieee.org>
To: rddunlap@osdl.org
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: vfs whitebox test
Date: 25 Nov 2003 10:33:50 -0700	[thread overview]
Message-ID: <1069781630.2848.14.camel@patrh9> (raw)
In-Reply-To: <20031125090930.281f7864.rddunlap@osdl.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".



  reply	other threads:[~2003-11-25 17:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24 23:29 vfs whitebox test Pat LaVarre
2003-11-25 15:46 ` Pat LaVarre
2003-11-25 17:04   ` Pat LaVarre
2003-11-25 17:06     ` Randy.Dunlap
2003-11-25 17:12     ` Pat LaVarre
2003-11-25 19:59       ` Pat LaVarre
2003-11-25 17:09   ` Randy.Dunlap
2003-11-25 17:33     ` Pat LaVarre [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-12-04 19:14 Pat LaVarre
2003-12-05 18:12 ` Pat LaVarre

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=1069781630.2848.14.camel@patrh9 \
    --to=p.lavarre@ieee.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=rddunlap@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.