From 53e5699fe863f0a122c73782b4465296e3adc131 Mon Sep 17 00:00:00 2001 From: Josh Stone Date: Wed, 16 Sep 2009 14:17:10 -0700 Subject: Add meta for the netdev example & regenerate indexes --- testsuite/systemtap.examples/index.html | 3 +++ 1 file changed, 3 insertions(+) (limited to 'testsuite/systemtap.examples/index.html') diff --git a/testsuite/systemtap.examples/index.html b/testsuite/systemtap.examples/index.html index b079f5b8..d3efe7fa 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -121,6 +121,9 @@ keywords: NETWORK network/dropwatch.stp - Watch Where Socket Buffers are Freed in the Kernel
keywords: NETWORK TRACEPOINT BUFFER FREE

Every five seconds the dropwatch.stp script lists the number of 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

    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.

    • -- cgit From ad7e33d7ceb3251f5141b586dad4f824c519d757 Mon Sep 17 00:00:00 2001 From: Josh Stone Date: Wed, 16 Sep 2009 15:16:47 -0700 Subject: Spelling fixes in the meta of many examples --- testsuite/systemtap.examples/index.html | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) (limited to 'testsuite/systemtap.examples/index.html') diff --git a/testsuite/systemtap.examples/index.html b/testsuite/systemtap.examples/index.html index d3efe7fa..203bc5d4 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -66,16 +66,16 @@ keywords: IO io/ioblktime.stp - Average Time Block IO Requests Spend in Queue
    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 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 line.

    +

    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 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 line.

  • 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 takes one argument which is the number of seconds between reports.

    • +

    The iostat-scsi.stp script provides a breakdown of the number of blks read and written on the machine's various SCSI devices. The script takes one argument which is the number of seconds between reports.

  • io/iostats.stp - List Executables Reading and Writing the Most Data
    keywords: IO PROFILING

    The iostat.stp script measures the amount of data successfully read and written by all the executables on the system. The output is sorted from most greatest sum of bytes read and written by an executable to the least. The output contains the count of operations (opens, reads, and writes), the totals and averages for the number of bytes read and written.

  • io/iotime.stp - Trace Time Spent in Read and Write for Files
    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.

    • +

    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 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 syscalls.

  • io/iotop.stp - Periodically Print I/O Activity by Process Name
    keywords: IO

    Every five seconds print out the top ten executables generating I/O traffic during that interval sorted in descending order.

    • @@ -105,16 +105,16 @@ keywords: MEMORY

    The mmfilepage.stp script uses the virtual memory tracepoints available in some kernels to track the number of faults, copy on writes mapping, and unmapping operations for file backed pages. When the script is terminated the counts are printed for each process that allocated pages while the script was running. The mmfilepage.stp script is useful in debugging leaks in the mapped file regions of a process.

  • 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.

    • +

    The mmreclaim.stp script uses the virtual memory tracepoints 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
    keywords: MEMORY
    -

    The mmwriteback.stp script uses the virtual memory tracepoints 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.

    • +

    The mmwriteback.stp script uses the virtual memory tracepoints 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 unexpected IO.

  • memory/numa_faults.stp - Summarize Process Misses across NUMA Nodes
    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 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.

    • +

    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 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.

  • memory/pfaults.stp - Generate Log of Major and Minor Page Faults
    keywords: MEMORY
    -

    The pfaults.stp script generates a simple log for each major and minor page fault that occurs on the system. Each line contains a timestamp (in microseconds) when the page fault servicing was 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.

    • +

    The pfaults.stp script generates a simple log for each major and minor page fault that occurs on the system. Each line contains a timestamp (in microseconds) when the page fault servicing was 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 occurring.

  • network/autofs4.stp - Watch autofs4 operations
    keywords: NETWORK AUTOFS NFS

    Trace key autofs4 operations such as mounting or unmounting remote filesystems.

    • @@ -171,7 +171,7 @@ keywords: SIGNALS

    Print signal counts by process name in descending order.

  • process/sigkill.stp - Track SIGKILL 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.

    • +

    The script traces any SIGKILL signals. When that SIGKILL signal is sent to a process, the script prints out the signal name, the destination executable and process ID, the executable name user ID that sent the signal.

  • process/sigmon.stp - Track a particular signal to a specific process
    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.

    • @@ -180,16 +180,16 @@ keywords: IO
  • process/sleeptime.stp - Trace Time Spent in nanosleep Syscalls
    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.

    • +

    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 parentheses, the "nanosleep:" key, and the duration of the sleep in microseconds.

  • process/syscalls_by_pid.stp - System-Wide Count of Syscalls by PID
    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
    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.

    • +

    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 greatest to least number of syscalls.

  • process/wait4time.stp - Trace Time Spent in wait4 Syscalls
    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".

    • +

    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 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".

  • profiling/functioncallcount.stp - Count Times Functions Called
    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.

    • -- cgit From ac505f97f1e85d95c9fe2b0401a375c2c8cd1cb9 Mon Sep 17 00:00:00 2001 From: Josh Stone Date: Wed, 16 Sep 2009 15:52:17 -0700 Subject: Add the badname.stp example This is a toy script I wrote a while back to demonstrate how SystemTap could be used to enforce filesystem naming rules. --- testsuite/systemtap.examples/index.html | 3 +++ 1 file changed, 3 insertions(+) (limited to 'testsuite/systemtap.examples/index.html') diff --git a/testsuite/systemtap.examples/index.html b/testsuite/systemtap.examples/index.html index 203bc5d4..cd2faadb 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -46,6 +46,9 @@ keywords: FORMAT
  • general/ansi_colors2.stp - Show Attribues in Table for ansi_set_color3()
    keywords: FORMAT

    The script prints a table showing the available attributes (bold, underline, and inverse) with color combinations for the 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

    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.

    • -- cgit From 6287a9e628bcbe6192da8fd9f0ce659a8acc13fc Mon Sep 17 00:00:00 2001 From: Mark Wielaard Date: Thu, 17 Sep 2009 15:44:52 +0200 Subject: Regenerate examples index. --- testsuite/systemtap.examples/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'testsuite/systemtap.examples/index.html') diff --git a/testsuite/systemtap.examples/index.html b/testsuite/systemtap.examples/index.html index cd2faadb..ba0d0fd7 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -48,7 +48,7 @@ keywords: FORMAT

    The script prints a table showing the available attributes (bold, underline, and inverse) with color combinations for the 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.

    • +

    The badname.stp script shows how one could prevent the creation of files with undesirable names using guru mode.

  • general/graphs.stp - Graphing Disk and CPU Utilization
    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.

    • -- cgit