diff options
Diffstat (limited to 'testsuite/systemtap.examples/index.txt')
| -rw-r--r-- | testsuite/systemtap.examples/index.txt | 40 |
1 files changed, 27 insertions, 13 deletions
diff --git a/testsuite/systemtap.examples/index.txt b/testsuite/systemtap.examples/index.txt index 376c545e..2e096ab1 100644 --- a/testsuite/systemtap.examples/index.txt +++ b/testsuite/systemtap.examples/index.txt @@ -17,6 +17,13 @@ keywords: format ans_set_color3() function in the ansi.stp tapset. +general/badname.stp - Bad Filename Filter +keywords: filesystem hack + + The badname.stp script shows how one could prevent the creation of + files with undesirable names. + + general/graphs.stp - Graphing Disk and CPU Utilization keywords: disk cpu use graph @@ -74,7 +81,7 @@ keywords: io The ioblktime.stp script tracks the amount of time that each block IO requests spend waiting for completion. The script computes the average time waiting time for block IO per device and prints list - every 10 seconds. In some cases there can be too many oustanding + every 10 seconds. In some cases there can be too many outstanding block IO operations and the script may exceed the default number of MAXMAPENTRIES allowed. In this case the allowed number can be increased with "-DMAXMAPENTRIES=10000" option on the stap command @@ -85,7 +92,7 @@ io/iostat-scsi.stp - iostat for SCSI Devices keywords: io profiling scsi The iostat-scsi.stp script provides a breakdown of the number of blks - read and written on the various machines's SCSI devices. The script + read and written on the machine's various SCSI devices. The script takes one argument which is the number of seconds between reports. @@ -109,7 +116,7 @@ keywords: syscall read write time io number of bytes read and written. When a file is closed the script prints out a pair of lines for the file. Both lines begin with a timestamp in microseconds, the PID number, and the executable name in - parenthesese. The first line with the "access" keyword lists the file + parentheses. The first line with the "access" keyword lists the file name, the attempted number of bytes for the read and write operations. The second line with the "iotime" keyword list the file name and the number of microseconds accumulated in the read and write @@ -212,9 +219,9 @@ memory/mmreclaim.stp - Track Virtual Memory System Page Reclamation keywords: memory The mmreclaim.stp script uses the virtual memory tracepoints - available in some kernels to track page reclaim activity that occured - while the script was running. Its useful is debugging performance - problems that occur due to page reclamation. + available in some kernels to track page reclaim activity that + occurred while the script was running. Its useful is debugging + performance problems that occur due to page reclamation. memory/mmwriteback.stp - Track Virtual Memory System Writing to Disk @@ -224,7 +231,7 @@ keywords: memory available in some kernels to report all of the file writebacks that occur form kupdate, pdflush and kjournald while the script is running. Its useful in determining where writes are coming from on a - supposedly idle system that is experiencing upexpected IO. + supposedly idle system that is experiencing unexpected IO. memory/numa_faults.stp - Summarize Process Misses across NUMA Nodes @@ -232,7 +239,7 @@ keywords: memory numa The numa_faults.stp script tracks the read and write pages faults for each process. When the script exits it prints out the total read and - write pages faults for each process. The script also providea a break + write pages faults for each process. The script also provide a break down of page faults per node for each process. This script is useful for determining whether the program has good locality (page faults limited to a single node) on a NUMA computer. @@ -247,7 +254,7 @@ keywords: memory completed, the pid of the process, the address of the page fault, the type of access (read or write), the type of fault (major or minor), and the elapsed time for page fault. This log can be examined to - determine where the page faults are occuring. + determine where the page faults are occurring. network/autofs4.stp - Watch autofs4 operations @@ -264,6 +271,13 @@ keywords: network tracepoint buffer free socket buffers freed at locations in the kernel. +network/netdev.stp - Trace Activity on Network Devices +keywords: network device traffic + + The netdev.stp script traces configuration and transmit/receive + activity on network devices. + + network/nettop.stp - Periodic Listing of Processes Using Network Interfaces keywords: network traffic per-process @@ -405,7 +419,7 @@ keywords: signals The script traces any SIGKILL signals. When that SIGKILL signal is sent to a process, the script prints out the signal name, the - desination executable and process ID, the executable name user ID + destination executable and process ID, the executable name user ID that sent the signal. @@ -434,7 +448,7 @@ keywords: syscall sleep The script watches each nanosleep syscall on the system. At the end of each nanosleep syscall the script prints out a line with a timestamp in microseconds, the pid, the executable name in - paretheses, the "nanosleep:" key, and the duration of the sleep in + parentheses, the "nanosleep:" key, and the duration of the sleep in microseconds. @@ -451,7 +465,7 @@ keywords: syscall The script watches all syscall on the system. On exit the script prints a list showing the number of systemcalls executed by each - executable ordered from greates to least number of syscalls. + executable ordered from greatest to least number of syscalls. process/wait4time.stp - Trace Time Spent in wait4 Syscalls @@ -459,7 +473,7 @@ keywords: syscall wait4 The script watches each wait4 syscall on the system. At the end of each wait4 syscall the script prints out a line with a timestamp in - microseconds, the pid, the executable name in paretheses, the + microseconds, the pid, the executable name in parentheses, the "wait4:" key, the duration of the wait and the PID that the wait4 was waiting for. If the waited for PID is not specified , it is "-1". |