summaryrefslogtreecommitdiffstats
path: root/testsuite/systemtap.examples/subsystem-index.txt
diff options
context:
space:
mode:
authorDave Brolley <brolley@redhat.com>2008-08-08 15:15:19 -0400
committerDave Brolley <brolley@redhat.com>2008-08-08 15:15:19 -0400
commit71906647386a9684086b0542318b536d95ae089c (patch)
treefb0348d7bb34095e95ad830da8e832bad9187a55 /testsuite/systemtap.examples/subsystem-index.txt
parentd5658775da9fa0ac792eb3f874df9f7c4d60de7e (diff)
parentf1118e1032612170cae8cd979cd529722ad95fdb (diff)
downloadsystemtap-steved-71906647386a9684086b0542318b536d95ae089c.tar.gz
systemtap-steved-71906647386a9684086b0542318b536d95ae089c.tar.xz
systemtap-steved-71906647386a9684086b0542318b536d95ae089c.zip
Merge branch 'master' of ssh://sources.redhat.com/git/systemtap
Conflicts: ChangeLog testsuite/ChangeLog
Diffstat (limited to 'testsuite/systemtap.examples/subsystem-index.txt')
-rw-r--r--testsuite/systemtap.examples/subsystem-index.txt242
1 files changed, 242 insertions, 0 deletions
diff --git a/testsuite/systemtap.examples/subsystem-index.txt b/testsuite/systemtap.examples/subsystem-index.txt
new file mode 100644
index 00000000..98e75e98
--- /dev/null
+++ b/testsuite/systemtap.examples/subsystem-index.txt
@@ -0,0 +1,242 @@
+SYSTEMTAP EXAMPLES INDEX BY SUBSYSTEM
+(see also index.txt, keyword-index.txt)
+
+= CPU =
+
+general/graphs.stp - Graphing Disk and CPU Utilization
+subsystems: disk cpu, keywords: disk cpu use graph
+
+ The script tracks the disk and CPU utilization. The resulting output
+ of the script can be piped into gnuplot to generate a graph of disk
+ and CPU USE.
+
+
+= DISK =
+
+general/graphs.stp - Graphing Disk and CPU Utilization
+subsystems: disk cpu, keywords: disk cpu use graph
+
+ The script tracks the disk and CPU utilization. The resulting output
+ of the script can be piped into gnuplot to generate a graph of disk
+ and CPU USE.
+
+
+io/disktop.stp - Summarize Disk Read/Write Traffic
+subsystems: disk, keywords: disk
+
+ Get the status of reading/writing disk every 5 seconds, output top
+ ten entries during that period.
+
+
+= IO =
+
+io/io_submit.stp - Tally Reschedule Reason During AIO io_submit Call
+subsystems: io, keywords: io backtrace
+
+ When a reschedule occurs during an AIO io_submit call, accumulate the
+ traceback in a histogram. When the script exits prints out a sorted
+ list from most common to least common backtrace.
+
+
+io/iotop.stp - Periodically Print I/O Activity by Process Name
+subsystems: io, keywords: io
+
+ Every five seconds print out the top ten executables generating I/O
+ traffic during that interval sorted in descending order.
+
+
+io/traceio.stp - Track Cumulative I/O Activity by Process Name
+subsystems: io, keywords: io
+
+ Every second print out the top ten executables sorted in descending
+ order based on cumulative I/O traffic observed.
+
+
+io/traceio2.stp - Watch I/O Activity on a Particular Device
+subsystems: io, keywords: io
+
+ Print out the executable name and process number as reads and writes
+ to the specified device occur.
+
+
+= KERNEL =
+
+general/para-callgraph.stp - Tracing Calls for Sections of Code
+subsystems: kernel, keywords: trace callgraph
+
+ The script takes two arguments: the first argument is the function to
+ starts/stops the per thread call graph traces and the second argument
+ is the list of functions to generate trace information on. The script
+ prints out a timestap for the thread, the function name and pid,
+ followed by entry or exit symboly and function name.
+
+
+process/pf2.stp - Profile kernel functions
+subsystems: kernel, keywords: profiling
+
+ The pf2.stp script sets up time-based sampling. Every five seconds it
+ prints out a sorted list with the top ten kernel functions with
+ samples.
+
+
+profiling/functioncallcount.stp - Count Times Functions Called
+subsystems: kernel, keywords: profiling functions
+
+ The functioncallcount.stp script takes one argument, a list of
+ functions to probe. The script will run and count the number of times
+ that each of the functions on the list is called. On exit the script
+ will print a sorted list from most frequently to least frequently
+ called function.
+
+
+profiling/thread-times.stp - Profile kernel functions
+subsystems: kernel, keywords: profiling
+
+ The thread-times.stp script sets up time-based sampling. Every five
+ seconds it prints out a sorted list with the top twenty processes
+ with samples broken down into percentage total time spent in
+ user-space and kernel-space.
+
+
+= LOCKING =
+
+process/futexes.stp - System-Wide Futex Contention
+subsystems: locking, keywords: syscall locking futex
+
+ The script watches the futex syscall on the system. On exit the
+ futexes address, the number of contentions, and the average time for
+ each contention on the futex are printed from lowest pid number to
+ highest.
+
+
+= NETWORK =
+
+network/nettop.stp - Periodic Listing of Processes Using Network Interfaces
+subsystems: network, keywords: network traffic per-process
+
+ Every five seconds the nettop.stp script prints out a list of
+ processed (PID and command) with the number of packets sent/received
+ and the amount of data sent/received by the process during that
+ interval.
+
+
+network/socket-trace.stp - Trace Functions called in Network Socket Code
+subsystems: network, keywords: network socket
+
+ The script instrument each of the functions inn the Linux kernel's
+ net/socket.c file. The script prints out trace. The first element of
+ a line is time delta in microseconds from the previous entry. This
+ is followed by the command name and the PID. The "->" and "<-"
+ indicates function entry and function exit, respectively. The last
+ element of the line is the function name.
+
+
+= NONE =
+
+general/helloworld.stp - SystemTap "Hello World" Program
+subsystems: none, keywords: simple
+
+ A basic "Hello World" program implemented in SystemTap script. It
+ prints out "hello world" message and then immediately exits.
+
+
+= SCHEDULER =
+
+process/sleepingBeauties.stp - Generating Backtraces of Threads Waiting for IO Operations
+subsystems: scheduler, keywords: io scheduler
+
+ The script monitor time threads spend waiting for IO operations (in
+ "D" state) in the wait_for_completion function. If a thread spends
+ over 10ms wall-clock time waiting, information is printed out
+ describing the thread number and executable name. When slow the
+ wait_for_completion function complete, backtraces for the long
+ duration calls are printed out.
+
+
+= SIGNALS =
+
+process/sig_by_pid.stp - Signal Counts by Process ID
+subsystems: signals, keywords: signals
+
+ Print signal counts by process ID in descending order.
+
+
+process/sig_by_proc.stp - Signal Counts by Process Name
+subsystems: signals, keywords: signals
+
+ Print signal counts by process name in descending order.
+
+
+process/sigkill.stp - Track SIGKILL Signals
+subsystems: signals, 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
+ that sent the signal.
+
+
+process/syscalls_by_pid.stp - System-Wide Count of Syscalls by PID
+subsystems: signals, keywords: signals
+
+ The script watches for a particular signal sent to a specific
+ process. When that signal is sent to the specified process, the
+ script prints out the PID and executable of the process sending the
+ signal, the PID and executable name of the process receiving the
+ signal, and the signal number and name.
+
+
+= SYSCALL =
+
+io/iotime.stp - Trace Time Spent in Read and Write for Files
+subsystems: syscall, keywords: syscall read write time io
+
+ The script watches each open, close, read, and write syscalls on the
+ system. For each file the scripts observes opened it accumulates the
+ amount of wall clock time spend in read and write operations and the
+ 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
+ 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
+ syscalls.
+
+
+process/sleeptime.stp - Trace Time Spent in nanosleep Syscalls
+subsystems: syscall, 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
+ microseconds.
+
+
+process/syscalls_by_pid.stp - System-Wide Count of Syscalls by PID
+subsystems: syscall, 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 PID
+ ordered from greatest to least number of syscalls.
+
+
+process/syscalls_by_proc.stp - System-Wide Count of Syscalls by Executable
+subsystems: syscall, 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.
+
+
+process/wait4time.stp - Trace Time Spent in wait4 Syscalls
+subsystems: syscall, 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
+ "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".
+
+