path: root/tools/perf/Documentation
diff options
authorRandy Dunlap <>2010-03-31 11:31:00 -0700
committerArnaldo Carvalho de Melo <>2010-04-08 11:34:26 -0300
commit854c5548dfad017920a36201d40449fdbad90bfb (patch)
treea9b5b7ef13c8c906ce2252b58c512bb3c245b465 /tools/perf/Documentation
parentf0e9c4fcefa42b5d28b915768dab81a7fdbbc00c (diff)
perf: cleanup some Documentation
Correct typos in perf bench & perf sched help text. Cc: Peter Zijlstra <>, Cc: Paul Mackerras <> LKML-Reference: <> Signed-off-by: Randy Dunlap <>
Diffstat (limited to 'tools/perf/Documentation')
2 files changed, 5 insertions, 5 deletions
diff --git a/tools/perf/Documentation/perf-bench.txt b/tools/perf/Documentation/perf-bench.txt
index ae525ac5a2ce..0181dddf6b61 100644
--- a/tools/perf/Documentation/perf-bench.txt
+++ b/tools/perf/Documentation/perf-bench.txt
@@ -19,12 +19,12 @@ COMMON OPTIONS
Specify format style.
-Current available format styles are,
+Current available format styles are:
Default style. This is mainly for human reading.
-% perf bench sched pipe # with no style specify
+% perf bench sched pipe # with no style specified
(executing 1000000 pipe operations between two tasks)
Total time:5.855 sec
5.855061 usecs/op
@@ -79,7 +79,7 @@ options (20 sender and receiver processes per group)
Total time:0.308 sec
-% perf bench sched messaging -t -g 20 # be multi-thread,with 20 groups
+% perf bench sched messaging -t -g 20 # be multi-thread, with 20 groups
(20 sender and receiver threads per group)
(20 groups == 800 threads run)
diff --git a/tools/perf/Documentation/perf-sched.txt b/tools/perf/Documentation/perf-sched.txt
index 1ce79198997b..8417644a6166 100644
--- a/tools/perf/Documentation/perf-sched.txt
+++ b/tools/perf/Documentation/perf-sched.txt
@@ -12,7 +12,7 @@ SYNOPSIS
-There's four variants of perf sched:
+There are four variants of perf sched:
'perf sched record <command>' to record the scheduling events
of an arbitrary workload.
@@ -27,7 +27,7 @@ There's four variants of perf sched:
via perf sched record. (this is done by starting up mockup threads
that mimic the workload based on the events in the trace. These
threads can then replay the timings (CPU runtime and sleep patterns)
- of the workload as it occured when it was recorded - and can repeat
+ of the workload as it occurred when it was recorded - and can repeat
it a number of times, measuring its performance.)