1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
|
Index: lmbench-3.0-a9+debian.1/doc/lat_mmap.8
===================================================================
--- lmbench-3.0-a9+debian.1.orig/doc/lat_mmap.8
+++ lmbench-3.0-a9+debian.1/doc/lat_mmap.8
@@ -18,7 +18,7 @@ lat_mmap \- costs of mmapping and unmmap
.SH DESCRIPTION
.B lat_mmap
times how fast a mapping can be made and unmade. This is useful because it
-is a fundemental part of processes that use SunOS style shared libraries
+is a fundamental part of processes that use SunOS style shared libraries
(the libraries are mapped in at process start up time and unmapped at
process exit).
.LP
Index: lmbench-3.0-a9+debian.1/doc/lmbench.8
===================================================================
--- lmbench-3.0-a9+debian.1.orig/doc/lmbench.8
+++ lmbench-3.0-a9+debian.1/doc/lmbench.8
@@ -37,7 +37,7 @@ the results it reports. The default num
.I repetitions
is 11.
.SH BANDWIDTH MEASUREMENTS
-Data movement is fundemental to the performance on most computer systems.
+Data movement is fundamental to the performance on most computer systems.
The bandwidth measurements are intended to show how the system can move
data. The results of the bandwidth metrics can be compared but care
must be taken to understand what it is that is being compared. The
@@ -75,7 +75,7 @@ reading of data via a TCP/IP socket.
bw_unix
reading data from a UNIX socket.
.SH LATENCY MEASUREMENTS
-Control messages are also fundemental to the performance on most
+Control messages are also fundamental to the performance on most
computer systems. The latency measurements are intended to show how fast
a system can be told to do some operation. The results of the
latency metrics can be compared to each other
|
