From: Michal Ostrowski <mostrows@styx.uwaterloo.ca>
To: linux-mm@kvack.org
Subject: Poor I/O Performance (test program attached)
Date: Thu, 1 Jun 2000 07:18:46 -0400 (EDT) [thread overview]
Message-ID: <14646.18070.554583.303619@styx.uwaterloo.ca> (raw)
[-- Attachment #1: message body text --]
[-- Type: text/plain, Size: 514 bytes --]
It was suggested to me to post the program with which I did my
testing. And so, by popular demand, the code is attached.
You can compile the code using: "gcc -o vmtest vmtest.c"
The command line options are described within the comments at the top
of the source file.
I ran my tests with:
dd if=/dev/zero of=bigfile count=250000 bs=4096
time vmtest file bigfile threads 10 itr 1000 blocks 32 size 1000000000
(repeat last line, altering parameters as necessary)
Michal Ostrowski
mostrows@styx.uwaterloo.ca
[-- Attachment #2: vmtest.c.gz --]
[-- Type: application/octet-stream, Size: 1410 bytes --]
reply other threads:[~2000-06-01 11:18 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=14646.18070.554583.303619@styx.uwaterloo.ca \
--to=mostrows@styx.uwaterloo.ca \
--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