aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSteven Rostedt <srostedt@redhat.com>2010-04-09 16:33:55 -0400
committerSteven Rostedt <rostedt@goodmis.org>2010-04-09 16:35:10 -0400
commit7f16dcb25f80f09978c762e23aca70882397ab05 (patch)
treea88fa876d6663adc151cb19104fd456d4c1688c0
parent04b2e439a93677bc6ef5035729bf05e7427ac13e (diff)
doc: Use timestamp and timeline instead of time stamp and time line
The document is inconsistent with its use of time stamp and timestamp as well as time line and timeline. This patch changes them all to be single words, except when referencing the GUI labels which have the space. Reported-by: Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
-rw-r--r--Documentation/HTML/index.html10
1 files changed, 5 insertions, 5 deletions
diff --git a/Documentation/HTML/index.html b/Documentation/HTML/index.html
index 331baf4..12c9957 100644
--- a/Documentation/HTML/index.html
+++ b/Documentation/HTML/index.html
@@ -79,8 +79,8 @@ and the plot area:
79 79
80<p> 80<p>
81The plot area contains the data of the given plot, where plots can be per CPU or 81The plot area contains the data of the given plot, where plots can be per CPU or
82per task. The top of the plot area shows a time line. The numbers in the time 82per task. The top of the plot area shows a timeline. The numbers in the timeline
83line are seconds. The time in the time line is taken from the timestamps within 83are seconds. The time in the timeline is taken from the timestamps within
84the trace.dat file which are architecture dependent. The time usually is the timestamp 84the trace.dat file which are architecture dependent. The time usually is the timestamp
85from when the system started. 85from when the system started.
86</p> 86</p>
@@ -224,9 +224,9 @@ Note that setting the cursor with double click will also set Marker A.
224 224
225<p> 225<p>
226The graph data is represented by plots. The data on the plots is either CPU specific or 226The graph data is represented by plots. The data on the plots is either CPU specific or
227task specific. If it is CPU specific, then the data is the time line of events that 227task specific. If it is CPU specific, then the data is the timeline of events that
228happened on a given CPU (which CPU is shown in the <a href="#graph-plot-title">plot title area</a>). 228happened on a given CPU (which CPU is shown in the <a href="#graph-plot-title">plot title area</a>).
229If the plot is task specific, then the time line of events is for the given 229If the plot is task specific, then the timeline of events is for the given
230task regardless of what CPU it was on at the time. The task name is also shown 230task regardless of what CPU it was on at the time. The task name is also shown
231in the plot title area. 231in the plot title area.
232</p> 232</p>
@@ -331,7 +331,7 @@ The columns of the list are:
331<ul> 331<ul>
332<li><b>#</b> - the index into the list. 332<li><b>#</b> - the index into the list.
333<li><b>CPU</b> - the CPU that the event occurred on. 333<li><b>CPU</b> - the CPU that the event occurred on.
334<li><b>Time Stamp</b> - The time stamp of the event. This is in seconds with microsecond 334<li><b>Time Stamp</b> - The timestamp of the event. This is in seconds with microsecond
335resolution. 335resolution.
336<li><b>PID</b> - The process ID of the task that was running when the event occurred. 336<li><b>PID</b> - The process ID of the task that was running when the event occurred.
337<li><b><a name="latency">Latency</a></b> - The latency is broken into 5 fields: 337<li><b><a name="latency">Latency</a></b> - The latency is broken into 5 fields: