]>
Commit | Line | Data |
---|---|---|
210ff7bf | 1 | SYSTEMTAP EXAMPLES INDEX BY KEYWORD |
09a98ae0 | 2 | (see also index.txt) |
210ff7bf FCE |
3 | |
4 | = BACKTRACE = | |
5 | ||
1cc8a4c7 WC |
6 | interrupt/scf.stp - Tally Backtraces for Inter-Processor Interrupt (IPI) |
7 | keywords: interrupt backtrace | |
8 | ||
9 | The Linux kernel function smp_call_function causes expensive | |
10 | inter-processor interrupts (IPIs). The scf.stp script tallies the | |
11 | processes and backtraces causing the interprocessor interrupts to | |
12 | identify the cause of the expensive IPI. On exit the script prints | |
13 | the tallies in descending frequency. | |
14 | ||
15 | ||
210ff7bf | 16 | io/io_submit.stp - Tally Reschedule Reason During AIO io_submit Call |
09a98ae0 | 17 | keywords: io backtrace |
210ff7bf FCE |
18 | |
19 | When a reschedule occurs during an AIO io_submit call, accumulate the | |
20 | traceback in a histogram. When the script exits prints out a sorted | |
21 | list from most common to least common backtrace. | |
22 | ||
23 | ||
cae71dd3 | 24 | process/sleepingBeauties.stp - Generating Backtraces of Threads Waiting for IO Operations |
09a98ae0 | 25 | keywords: io scheduler backtrace |
cae71dd3 FCE |
26 | |
27 | The script monitors the time that threads spend waiting for IO | |
28 | operations (in "D" state) in the wait_for_completion function. If a | |
29 | thread spends over 10ms, its name and backtrace is printed, and later | |
30 | so is the total delay. | |
31 | ||
32 | ||
210ff7bf FCE |
33 | = CALLGRAPH = |
34 | ||
aa15b9f0 | 35 | general/para-callgraph.stp - Callgraph tracing with arguments |
09a98ae0 | 36 | keywords: trace callgraph |
210ff7bf | 37 | |
aa15b9f0 FCE |
38 | Print a timed per-thread callgraph, complete with function parameters |
39 | and return values. The first parameter names the function probe | |
40 | points to trace. The optional second parameter names the probe | |
41 | points for trigger functions, which acts to enable tracing for only | |
42 | those functions that occur while the current thread is nested within | |
43 | the trigger. | |
210ff7bf FCE |
44 | |
45 | ||
46 | = CPU = | |
47 | ||
48 | general/graphs.stp - Graphing Disk and CPU Utilization | |
09a98ae0 | 49 | keywords: disk cpu use graph |
210ff7bf FCE |
50 | |
51 | The script tracks the disk and CPU utilization. The resulting output | |
52 | of the script can be piped into gnuplot to generate a graph of disk | |
53 | and CPU USE. | |
54 | ||
55 | ||
56 | = DISK = | |
57 | ||
58 | general/graphs.stp - Graphing Disk and CPU Utilization | |
09a98ae0 | 59 | keywords: disk cpu use graph |
210ff7bf FCE |
60 | |
61 | The script tracks the disk and CPU utilization. The resulting output | |
62 | of the script can be piped into gnuplot to generate a graph of disk | |
63 | and CPU USE. | |
64 | ||
65 | ||
66 | io/disktop.stp - Summarize Disk Read/Write Traffic | |
09a98ae0 | 67 | keywords: disk |
210ff7bf FCE |
68 | |
69 | Get the status of reading/writing disk every 5 seconds, output top | |
70 | ten entries during that period. | |
71 | ||
72 | ||
73 | = FUNCTIONS = | |
74 | ||
75 | profiling/functioncallcount.stp - Count Times Functions Called | |
09a98ae0 | 76 | keywords: profiling functions |
210ff7bf FCE |
77 | |
78 | The functioncallcount.stp script takes one argument, a list of | |
79 | functions to probe. The script will run and count the number of times | |
80 | that each of the functions on the list is called. On exit the script | |
81 | will print a sorted list from most frequently to least frequently | |
82 | called function. | |
83 | ||
84 | ||
85 | = FUTEX = | |
86 | ||
87 | process/futexes.stp - System-Wide Futex Contention | |
09a98ae0 | 88 | keywords: syscall locking futex |
210ff7bf FCE |
89 | |
90 | The script watches the futex syscall on the system. On exit the | |
91 | futexes address, the number of contentions, and the average time for | |
92 | each contention on the futex are printed from lowest pid number to | |
93 | highest. | |
94 | ||
95 | ||
96 | = GRAPH = | |
97 | ||
98 | general/graphs.stp - Graphing Disk and CPU Utilization | |
09a98ae0 | 99 | keywords: disk cpu use graph |
210ff7bf FCE |
100 | |
101 | The script tracks the disk and CPU utilization. The resulting output | |
102 | of the script can be piped into gnuplot to generate a graph of disk | |
103 | and CPU USE. | |
104 | ||
105 | ||
1cc8a4c7 WC |
106 | = INTERRUPT = |
107 | ||
108 | interrupt/scf.stp - Tally Backtraces for Inter-Processor Interrupt (IPI) | |
109 | keywords: interrupt backtrace | |
110 | ||
111 | The Linux kernel function smp_call_function causes expensive | |
112 | inter-processor interrupts (IPIs). The scf.stp script tallies the | |
113 | processes and backtraces causing the interprocessor interrupts to | |
114 | identify the cause of the expensive IPI. On exit the script prints | |
115 | the tallies in descending frequency. | |
116 | ||
117 | ||
210ff7bf FCE |
118 | = IO = |
119 | ||
120 | io/io_submit.stp - Tally Reschedule Reason During AIO io_submit Call | |
09a98ae0 | 121 | keywords: io backtrace |
210ff7bf FCE |
122 | |
123 | When a reschedule occurs during an AIO io_submit call, accumulate the | |
124 | traceback in a histogram. When the script exits prints out a sorted | |
125 | list from most common to least common backtrace. | |
126 | ||
127 | ||
3e4444ed WC |
128 | io/iostats.stp - List Executables Reading and Writing the Most Data |
129 | keywords: io profiling | |
130 | ||
131 | The iostat.stp script measures the amount of data successfully read | |
132 | and written by all the executables on the system. The output is | |
133 | sorted from most greatest sum of bytes read and written by an | |
134 | executable to the least. The output contains the count of operations | |
135 | (opens, reads, and writes), the totals and averages for the number of | |
136 | bytes read and written. | |
137 | ||
138 | ||
210ff7bf | 139 | io/iotime.stp - Trace Time Spent in Read and Write for Files |
09a98ae0 | 140 | keywords: syscall read write time io |
210ff7bf FCE |
141 | |
142 | The script watches each open, close, read, and write syscalls on the | |
143 | system. For each file the scripts observes opened it accumulates the | |
144 | amount of wall clock time spend in read and write operations and the | |
145 | number of bytes read and written. When a file is closed the script | |
146 | prints out a pair of lines for the file. Both lines begin with a | |
147 | timestamp in microseconds, the PID number, and the executable name in | |
148 | parenthesese. The first line with the "access" keyword lists the file | |
149 | name, the attempted number of bytes for the read and write | |
150 | operations. The second line with the "iotime" keyword list the file | |
151 | name and the number of microseconds accumulated in the read and write | |
152 | syscalls. | |
153 | ||
154 | ||
155 | io/iotop.stp - Periodically Print I/O Activity by Process Name | |
09a98ae0 | 156 | keywords: io |
210ff7bf FCE |
157 | |
158 | Every five seconds print out the top ten executables generating I/O | |
159 | traffic during that interval sorted in descending order. | |
160 | ||
161 | ||
162 | io/traceio.stp - Track Cumulative I/O Activity by Process Name | |
09a98ae0 | 163 | keywords: io |
210ff7bf FCE |
164 | |
165 | Every second print out the top ten executables sorted in descending | |
166 | order based on cumulative I/O traffic observed. | |
167 | ||
168 | ||
169 | io/traceio2.stp - Watch I/O Activity on a Particular Device | |
09a98ae0 | 170 | keywords: io |
210ff7bf FCE |
171 | |
172 | Print out the executable name and process number as reads and writes | |
173 | to the specified device occur. | |
174 | ||
175 | ||
176 | process/sleepingBeauties.stp - Generating Backtraces of Threads Waiting for IO Operations | |
09a98ae0 | 177 | keywords: io scheduler backtrace |
210ff7bf | 178 | |
cae71dd3 FCE |
179 | The script monitors the time that threads spend waiting for IO |
180 | operations (in "D" state) in the wait_for_completion function. If a | |
181 | thread spends over 10ms, its name and backtrace is printed, and later | |
182 | so is the total delay. | |
210ff7bf FCE |
183 | |
184 | ||
185 | = LOCKING = | |
186 | ||
187 | process/futexes.stp - System-Wide Futex Contention | |
09a98ae0 | 188 | keywords: syscall locking futex |
210ff7bf FCE |
189 | |
190 | The script watches the futex syscall on the system. On exit the | |
191 | futexes address, the number of contentions, and the average time for | |
192 | each contention on the futex are printed from lowest pid number to | |
193 | highest. | |
194 | ||
195 | ||
196 | = NETWORK = | |
197 | ||
198 | network/nettop.stp - Periodic Listing of Processes Using Network Interfaces | |
09a98ae0 | 199 | keywords: network traffic per-process |
210ff7bf FCE |
200 | |
201 | Every five seconds the nettop.stp script prints out a list of | |
202 | processed (PID and command) with the number of packets sent/received | |
203 | and the amount of data sent/received by the process during that | |
204 | interval. | |
205 | ||
206 | ||
207 | network/socket-trace.stp - Trace Functions called in Network Socket Code | |
09a98ae0 | 208 | keywords: network socket |
210ff7bf FCE |
209 | |
210 | The script instrument each of the functions inn the Linux kernel's | |
211 | net/socket.c file. The script prints out trace. The first element of | |
212 | a line is time delta in microseconds from the previous entry. This | |
213 | is followed by the command name and the PID. The "->" and "<-" | |
214 | indicates function entry and function exit, respectively. The last | |
215 | element of the line is the function name. | |
216 | ||
217 | ||
492d227f WC |
218 | network/tcp_connections.stp - Track Creation of Incoming TCP Connections |
219 | keywords: network tcp socket | |
220 | ||
221 | The tcp_connections.stp script prints information for each new | |
222 | incoming TCP connection accepted by the computer. The information | |
223 | includes the UID, the command accepting the connection, the PID of | |
224 | the command, the port the connection is on, and the IP address of the | |
225 | originator of the request. | |
226 | ||
227 | ||
210ff7bf FCE |
228 | = PER-PROCESS = |
229 | ||
230 | network/nettop.stp - Periodic Listing of Processes Using Network Interfaces | |
09a98ae0 | 231 | keywords: network traffic per-process |
210ff7bf FCE |
232 | |
233 | Every five seconds the nettop.stp script prints out a list of | |
234 | processed (PID and command) with the number of packets sent/received | |
235 | and the amount of data sent/received by the process during that | |
236 | interval. | |
237 | ||
238 | ||
239 | = PROFILING = | |
240 | ||
3e4444ed WC |
241 | io/iostats.stp - List Executables Reading and Writing the Most Data |
242 | keywords: io profiling | |
243 | ||
244 | The iostat.stp script measures the amount of data successfully read | |
245 | and written by all the executables on the system. The output is | |
246 | sorted from most greatest sum of bytes read and written by an | |
247 | executable to the least. The output contains the count of operations | |
248 | (opens, reads, and writes), the totals and averages for the number of | |
249 | bytes read and written. | |
250 | ||
251 | ||
210ff7bf | 252 | process/pf2.stp - Profile kernel functions |
09a98ae0 | 253 | keywords: profiling |
210ff7bf FCE |
254 | |
255 | The pf2.stp script sets up time-based sampling. Every five seconds it | |
256 | prints out a sorted list with the top ten kernel functions with | |
257 | samples. | |
258 | ||
259 | ||
260 | profiling/functioncallcount.stp - Count Times Functions Called | |
09a98ae0 | 261 | keywords: profiling functions |
210ff7bf FCE |
262 | |
263 | The functioncallcount.stp script takes one argument, a list of | |
264 | functions to probe. The script will run and count the number of times | |
265 | that each of the functions on the list is called. On exit the script | |
266 | will print a sorted list from most frequently to least frequently | |
267 | called function. | |
268 | ||
269 | ||
270 | profiling/thread-times.stp - Profile kernel functions | |
09a98ae0 | 271 | keywords: profiling |
210ff7bf FCE |
272 | |
273 | The thread-times.stp script sets up time-based sampling. Every five | |
274 | seconds it prints out a sorted list with the top twenty processes | |
275 | with samples broken down into percentage total time spent in | |
276 | user-space and kernel-space. | |
277 | ||
278 | ||
ff90b297 WC |
279 | profiling/timeout.stp - Show Processes Doing Polling Operations |
280 | keywords: profiling | |
281 | ||
282 | The timeout.stp script is based on a blog entry | |
283 | (http://udrepper.livejournal.com/19041.html) mentioning a need for a | |
284 | tool to help developers find applications that are polling. The | |
285 | timeout.stp script monitors systemcall used for polling and records | |
286 | the systemcalls that timed out rather than returned because some | |
287 | action occurred. The script updates the screen once a second with the | |
288 | top twenty processes. | |
289 | ||
290 | ||
1bf72dfe WC |
291 | profiling/topsys.stp - Show Processes Doing Polling Operations |
292 | keywords: profiling | |
293 | ||
294 | The topsys.stp script lists out the top twenty systemcalls for the | |
295 | previous 5 seconds. The output is sorted from most frequent to least | |
296 | frequent. | |
297 | ||
298 | ||
210ff7bf FCE |
299 | = READ = |
300 | ||
301 | io/iotime.stp - Trace Time Spent in Read and Write for Files | |
09a98ae0 | 302 | keywords: syscall read write time io |
210ff7bf FCE |
303 | |
304 | The script watches each open, close, read, and write syscalls on the | |
305 | system. For each file the scripts observes opened it accumulates the | |
306 | amount of wall clock time spend in read and write operations and the | |
307 | number of bytes read and written. When a file is closed the script | |
308 | prints out a pair of lines for the file. Both lines begin with a | |
309 | timestamp in microseconds, the PID number, and the executable name in | |
310 | parenthesese. The first line with the "access" keyword lists the file | |
311 | name, the attempted number of bytes for the read and write | |
312 | operations. The second line with the "iotime" keyword list the file | |
313 | name and the number of microseconds accumulated in the read and write | |
314 | syscalls. | |
315 | ||
316 | ||
317 | = SCHEDULER = | |
318 | ||
319 | process/sleepingBeauties.stp - Generating Backtraces of Threads Waiting for IO Operations | |
09a98ae0 | 320 | keywords: io scheduler backtrace |
cae71dd3 FCE |
321 | |
322 | The script monitors the time that threads spend waiting for IO | |
323 | operations (in "D" state) in the wait_for_completion function. If a | |
324 | thread spends over 10ms, its name and backtrace is printed, and later | |
325 | so is the total delay. | |
210ff7bf FCE |
326 | |
327 | ||
328 | = SIGNALS = | |
329 | ||
330 | process/sig_by_pid.stp - Signal Counts by Process ID | |
09a98ae0 | 331 | keywords: signals |
210ff7bf FCE |
332 | |
333 | Print signal counts by process ID in descending order. | |
334 | ||
335 | ||
336 | process/sig_by_proc.stp - Signal Counts by Process Name | |
09a98ae0 | 337 | keywords: signals |
210ff7bf FCE |
338 | |
339 | Print signal counts by process name in descending order. | |
340 | ||
341 | ||
342 | process/sigkill.stp - Track SIGKILL Signals | |
09a98ae0 | 343 | keywords: signals |
210ff7bf FCE |
344 | |
345 | The script traces any SIGKILL signals. When that SIGKILL signal is | |
346 | sent to a process, the script prints out the signal name, the | |
347 | desination executable and process ID, the executable name user ID | |
348 | that sent the signal. | |
349 | ||
350 | ||
351 | process/syscalls_by_pid.stp - System-Wide Count of Syscalls by PID | |
09a98ae0 | 352 | keywords: signals |
210ff7bf FCE |
353 | |
354 | The script watches for a particular signal sent to a specific | |
355 | process. When that signal is sent to the specified process, the | |
356 | script prints out the PID and executable of the process sending the | |
357 | signal, the PID and executable name of the process receiving the | |
358 | signal, and the signal number and name. | |
359 | ||
360 | ||
361 | = SIMPLE = | |
362 | ||
363 | general/helloworld.stp - SystemTap "Hello World" Program | |
09a98ae0 | 364 | keywords: simple |
210ff7bf FCE |
365 | |
366 | A basic "Hello World" program implemented in SystemTap script. It | |
367 | prints out "hello world" message and then immediately exits. | |
368 | ||
369 | ||
370 | = SLEEP = | |
371 | ||
372 | process/sleeptime.stp - Trace Time Spent in nanosleep Syscalls | |
09a98ae0 | 373 | keywords: syscall sleep |
210ff7bf FCE |
374 | |
375 | The script watches each nanosleep syscall on the system. At the end | |
376 | of each nanosleep syscall the script prints out a line with a | |
377 | timestamp in microseconds, the pid, the executable name in | |
378 | paretheses, the "nanosleep:" key, and the duration of the sleep in | |
379 | microseconds. | |
380 | ||
381 | ||
382 | = SOCKET = | |
383 | ||
384 | network/socket-trace.stp - Trace Functions called in Network Socket Code | |
09a98ae0 | 385 | keywords: network socket |
210ff7bf FCE |
386 | |
387 | The script instrument each of the functions inn the Linux kernel's | |
388 | net/socket.c file. The script prints out trace. The first element of | |
389 | a line is time delta in microseconds from the previous entry. This | |
390 | is followed by the command name and the PID. The "->" and "<-" | |
391 | indicates function entry and function exit, respectively. The last | |
392 | element of the line is the function name. | |
393 | ||
394 | ||
492d227f WC |
395 | network/tcp_connections.stp - Track Creation of Incoming TCP Connections |
396 | keywords: network tcp socket | |
397 | ||
398 | The tcp_connections.stp script prints information for each new | |
399 | incoming TCP connection accepted by the computer. The information | |
400 | includes the UID, the command accepting the connection, the PID of | |
401 | the command, the port the connection is on, and the IP address of the | |
402 | originator of the request. | |
403 | ||
404 | ||
210ff7bf FCE |
405 | = SYSCALL = |
406 | ||
407 | io/iotime.stp - Trace Time Spent in Read and Write for Files | |
09a98ae0 | 408 | keywords: syscall read write time io |
210ff7bf FCE |
409 | |
410 | The script watches each open, close, read, and write syscalls on the | |
411 | system. For each file the scripts observes opened it accumulates the | |
412 | amount of wall clock time spend in read and write operations and the | |
413 | number of bytes read and written. When a file is closed the script | |
414 | prints out a pair of lines for the file. Both lines begin with a | |
415 | timestamp in microseconds, the PID number, and the executable name in | |
416 | parenthesese. The first line with the "access" keyword lists the file | |
417 | name, the attempted number of bytes for the read and write | |
418 | operations. The second line with the "iotime" keyword list the file | |
419 | name and the number of microseconds accumulated in the read and write | |
420 | syscalls. | |
421 | ||
422 | ||
423 | process/futexes.stp - System-Wide Futex Contention | |
09a98ae0 | 424 | keywords: syscall locking futex |
210ff7bf FCE |
425 | |
426 | The script watches the futex syscall on the system. On exit the | |
427 | futexes address, the number of contentions, and the average time for | |
428 | each contention on the futex are printed from lowest pid number to | |
429 | highest. | |
430 | ||
431 | ||
432 | process/sleeptime.stp - Trace Time Spent in nanosleep Syscalls | |
09a98ae0 | 433 | keywords: syscall sleep |
210ff7bf FCE |
434 | |
435 | The script watches each nanosleep syscall on the system. At the end | |
436 | of each nanosleep syscall the script prints out a line with a | |
437 | timestamp in microseconds, the pid, the executable name in | |
438 | paretheses, the "nanosleep:" key, and the duration of the sleep in | |
439 | microseconds. | |
440 | ||
441 | ||
442 | process/syscalls_by_pid.stp - System-Wide Count of Syscalls by PID | |
09a98ae0 | 443 | keywords: syscall |
210ff7bf FCE |
444 | |
445 | The script watches all syscall on the system. On exit the script | |
446 | prints a list showing the number of systemcalls executed by each PID | |
447 | ordered from greatest to least number of syscalls. | |
448 | ||
449 | ||
450 | process/syscalls_by_proc.stp - System-Wide Count of Syscalls by Executable | |
09a98ae0 | 451 | keywords: syscall |
210ff7bf FCE |
452 | |
453 | The script watches all syscall on the system. On exit the script | |
454 | prints a list showing the number of systemcalls executed by each | |
455 | executable ordered from greates to least number of syscalls. | |
456 | ||
457 | ||
458 | process/wait4time.stp - Trace Time Spent in wait4 Syscalls | |
09a98ae0 | 459 | keywords: syscall wait4 |
210ff7bf FCE |
460 | |
461 | The script watches each wait4 syscall on the system. At the end of | |
462 | each wait4 syscall the script prints out a line with a timestamp in | |
463 | microseconds, the pid, the executable name in paretheses, the | |
464 | "wait4:" key, the duration of the wait and the PID that the wait4 was | |
465 | waiting for. If the waited for PID is not specified , it is "-1". | |
466 | ||
467 | ||
492d227f WC |
468 | = TCP = |
469 | ||
470 | network/tcp_connections.stp - Track Creation of Incoming TCP Connections | |
471 | keywords: network tcp socket | |
472 | ||
473 | The tcp_connections.stp script prints information for each new | |
474 | incoming TCP connection accepted by the computer. The information | |
475 | includes the UID, the command accepting the connection, the PID of | |
476 | the command, the port the connection is on, and the IP address of the | |
477 | originator of the request. | |
478 | ||
479 | ||
210ff7bf FCE |
480 | = TIME = |
481 | ||
482 | io/iotime.stp - Trace Time Spent in Read and Write for Files | |
09a98ae0 | 483 | keywords: syscall read write time io |
210ff7bf FCE |
484 | |
485 | The script watches each open, close, read, and write syscalls on the | |
486 | system. For each file the scripts observes opened it accumulates the | |
487 | amount of wall clock time spend in read and write operations and the | |
488 | number of bytes read and written. When a file is closed the script | |
489 | prints out a pair of lines for the file. Both lines begin with a | |
490 | timestamp in microseconds, the PID number, and the executable name in | |
491 | parenthesese. The first line with the "access" keyword lists the file | |
492 | name, the attempted number of bytes for the read and write | |
493 | operations. The second line with the "iotime" keyword list the file | |
494 | name and the number of microseconds accumulated in the read and write | |
495 | syscalls. | |
496 | ||
497 | ||
498 | = TRACE = | |
499 | ||
aa15b9f0 | 500 | general/para-callgraph.stp - Callgraph tracing with arguments |
09a98ae0 | 501 | keywords: trace callgraph |
210ff7bf | 502 | |
aa15b9f0 FCE |
503 | Print a timed per-thread callgraph, complete with function parameters |
504 | and return values. The first parameter names the function probe | |
505 | points to trace. The optional second parameter names the probe | |
506 | points for trigger functions, which acts to enable tracing for only | |
507 | those functions that occur while the current thread is nested within | |
508 | the trigger. | |
210ff7bf FCE |
509 | |
510 | ||
511 | = TRAFFIC = | |
512 | ||
513 | network/nettop.stp - Periodic Listing of Processes Using Network Interfaces | |
09a98ae0 | 514 | keywords: network traffic per-process |
210ff7bf FCE |
515 | |
516 | Every five seconds the nettop.stp script prints out a list of | |
517 | processed (PID and command) with the number of packets sent/received | |
518 | and the amount of data sent/received by the process during that | |
519 | interval. | |
520 | ||
521 | ||
522 | = USE = | |
523 | ||
524 | general/graphs.stp - Graphing Disk and CPU Utilization | |
09a98ae0 | 525 | keywords: disk cpu use graph |
210ff7bf FCE |
526 | |
527 | The script tracks the disk and CPU utilization. The resulting output | |
528 | of the script can be piped into gnuplot to generate a graph of disk | |
529 | and CPU USE. | |
530 | ||
531 | ||
532 | = WAIT4 = | |
533 | ||
534 | process/wait4time.stp - Trace Time Spent in wait4 Syscalls | |
09a98ae0 | 535 | keywords: syscall wait4 |
210ff7bf FCE |
536 | |
537 | The script watches each wait4 syscall on the system. At the end of | |
538 | each wait4 syscall the script prints out a line with a timestamp in | |
539 | microseconds, the pid, the executable name in paretheses, the | |
540 | "wait4:" key, the duration of the wait and the PID that the wait4 was | |
541 | waiting for. If the waited for PID is not specified , it is "-1". | |
542 | ||
543 | ||
544 | = WRITE = | |
545 | ||
546 | io/iotime.stp - Trace Time Spent in Read and Write for Files | |
09a98ae0 | 547 | keywords: syscall read write time io |
210ff7bf FCE |
548 | |
549 | The script watches each open, close, read, and write syscalls on the | |
550 | system. For each file the scripts observes opened it accumulates the | |
551 | amount of wall clock time spend in read and write operations and the | |
552 | number of bytes read and written. When a file is closed the script | |
553 | prints out a pair of lines for the file. Both lines begin with a | |
554 | timestamp in microseconds, the PID number, and the executable name in | |
555 | parenthesese. The first line with the "access" keyword lists the file | |
556 | name, the attempted number of bytes for the read and write | |
557 | operations. The second line with the "iotime" keyword list the file | |
558 | name and the number of microseconds accumulated in the read and write | |
559 | syscalls. | |
560 | ||
561 |