summaryrefslogtreecommitdiffstats
path: root/share/doc/papers/diskperf
diff options
context:
space:
mode:
authorschweikh <schweikh@FreeBSD.org>2003-01-01 18:49:04 +0000
committerschweikh <schweikh@FreeBSD.org>2003-01-01 18:49:04 +0000
commitd3367c5f5d3ddcc6824d8f41c4cf179f9a5588f8 (patch)
treef412dafc7d29429919e8770cdefeb37441fc1299 /share/doc/papers/diskperf
parent718a7892bc6da2237db71c255051dd54a4e93a92 (diff)
downloadFreeBSD-src-d3367c5f5d3ddcc6824d8f41c4cf179f9a5588f8.zip
FreeBSD-src-d3367c5f5d3ddcc6824d8f41c4cf179f9a5588f8.tar.gz
Correct typos, mostly s/ a / an / where appropriate. Some whitespace cleanup,
especially in troff files.
Diffstat (limited to 'share/doc/papers/diskperf')
-rw-r--r--share/doc/papers/diskperf/motivation.ms4
-rw-r--r--share/doc/papers/diskperf/tests.ms6
2 files changed, 6 insertions, 4 deletions
diff --git a/share/doc/papers/diskperf/motivation.ms b/share/doc/papers/diskperf/motivation.ms
index 2884fc5..d5fde9d 100644
--- a/share/doc/papers/diskperf/motivation.ms
+++ b/share/doc/papers/diskperf/motivation.ms
@@ -31,6 +31,8 @@
.\"
.\" @(#)motivation.ms 6.2 (Berkeley) 4/16/91
.\"
+.\" $FreeBSD$
+.\"
.ds RH Motivation
.NH
Motivation
@@ -45,7 +47,7 @@ DEC has become, with the introduction of the UDA50/RA81 system,
cost competitive
in the area of disk storage for the first time.
Emulex's entry into the VAX 11/780 SBI controller
-field, the SC780, represented a important choice for us to examine, given
+field, the SC780, represented an important choice for us to examine, given
our previous success with their VAX 11/750 SC750 controller and
their UNIBUS controllers.
The Fujitsu 2351A
diff --git a/share/doc/papers/diskperf/tests.ms b/share/doc/papers/diskperf/tests.ms
index 40bbe0f..e937931 100644
--- a/share/doc/papers/diskperf/tests.ms
+++ b/share/doc/papers/diskperf/tests.ms
@@ -71,7 +71,7 @@ This is typical of most 4.2BSD user programs since a standard set of
I/O support routines is commonly used and these routines buffer
data in similar block sizes.
.PP
-For each test run, a empty eight Kilobyte block
+For each test run, an empty eight Kilobyte block
file system was created in the target
storage system.
Then each of the four tests was run and timed.
@@ -79,9 +79,9 @@ Each test was run three times;
the first to clear out any useful data in the cache,
and the second two to insure that the experiment
had stablized and was repeatable.
-Each test operated on eight Megabytes of data to
+Each test operated on eight Megabytes of data to
insure that the cache did not overly influence the results.
-Another file system was then initialized using a
+Another file system was then initialized using a
basic blocking factor of four Kilobytes and the same tests
were run again and timed.
A command script for a run appears as follows:
OpenPOWER on IntegriCloud