From ff90b2974f841b92434cb46d89c39f08d01cc966 Mon Sep 17 00:00:00 2001 From: William Cohen Date: Wed, 28 Jan 2009 16:03:01 -0500 Subject: Add the polling timeout example and update the catalog. --- 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 52bc294b..b67aa226 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -112,6 +112,9 @@ keywords: PROFILING profiling/thread-times.stp - Profile kernel functions
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.

+
  • profiling/timeout.stp - Show Processes Doing Polling Operations
    +keywords: PROFILING
    +

    The timeout.stp script is based on a blog entry (http://udrepper.livejournal.com/19041.html) mentioning a need for a tool to help developers find applications that are polling. The timeout.stp script monitors systemcall used for polling and records the systemcalls that timed out rather than returned because some action occurred. The script updates the screen once a second with the top twenty processes.

    • -- cgit From 1cc8a4c78bff79ea8b60e916e5cd01571b469b03 Mon Sep 17 00:00:00 2001 From: William Cohen Date: Fri, 30 Jan 2009 12:33:14 -0500 Subject: Move the scf.stp example from systemtap.samples to systemtap.examples. --- 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 b67aa226..87a5a50e 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -49,6 +49,9 @@ keywords: SIMPLE
  • general/para-callgraph.stp - Callgraph tracing with arguments
    keywords: TRACE CALLGRAPH

    Print a timed per-thread callgraph, complete with function parameters and return values. The first parameter names the function probe points to trace. The optional second parameter names the probe points for trigger functions, which acts to enable tracing for only those functions that occur while the current thread is nested within the trigger.

    • +
  • interrupt/scf.stp - Tally Backtraces for Inter-Processor Interrupt (IPI)
    +keywords: INTERRUPT BACKTRACE
    +

    The Linux kernel function smp_call_function causes expensive inter-processor interrupts (IPIs). The scf.stp script tallies the processes and backtraces causing the interprocessor interrupts to identify the cause of the expensive IPI. On exit the script prints the tallies in descending frequency.

  • io/disktop.stp - Summarize Disk Read/Write Traffic
    keywords: DISK

    Get the status of reading/writing disk every 5 seconds, output top ten entries during that period.

    • -- cgit From 492d227f2caa558c4fdcd4e7aae65cf32b4549cc Mon Sep 17 00:00:00 2001 From: William Cohen Date: Mon, 2 Feb 2009 11:18:01 -0500 Subject: Revise tcp_connections.stp example and place in sysemtap.examples directory. --- 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 87a5a50e..3395edca 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -76,6 +76,9 @@ keywords: NETWORK network/socket-trace.stp - Trace Functions called in Network Socket Code
    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.

    +
  • network/tcp_connections.stp - Track Creation of Incoming TCP Connections
    +keywords: NETWORK TCP SOCKET
    +

    The tcp_connections.stp script prints information for each new incoming TCP connection accepted by the computer. The information includes the UID, the command accepting the connection, the PID of the command, the port the connection is on, and the IP address of the originator of the request.

  • process/futexes.stp - System-Wide Futex Contention
    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.

    • -- cgit From 1bf72dfea404434f954214298367817d5c591903 Mon Sep 17 00:00:00 2001 From: William Cohen Date: Mon, 2 Feb 2009 14:21:25 -0500 Subject: Revised topsys.stp and moved to the testsuite/systemtap.examples directory. --- 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 3395edca..e02ab867 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -121,6 +121,9 @@ keywords: PROFILING
  • profiling/timeout.stp - Show Processes Doing Polling Operations
    keywords: PROFILING

    The timeout.stp script is based on a blog entry (http://udrepper.livejournal.com/19041.html) mentioning a need for a tool to help developers find applications that are polling. The timeout.stp script monitors systemcall used for polling and records the systemcalls that timed out rather than returned because some action occurred. The script updates the screen once a second with the top twenty processes.

    • +
  • profiling/topsys.stp - Show Processes Doing Polling Operations
    +keywords: PROFILING
    +

    The topsys.stp script lists out the top twenty systemcalls for the previous 5 seconds. The output is sorted from most frequent to least frequent.

    • -- cgit From 3e4444ed0b5367ee58c89685c2ee072abc185737 Mon Sep 17 00:00:00 2001 From: William Cohen Date: Fri, 6 Feb 2009 17:44:23 -0500 Subject: Fold the systemtap.samples/iotask*.stp into systemtap.examples/io/iostats.stp. Regenerate the catalog information. --- 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 e02ab867..17c520ef 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -58,6 +58,9 @@ keywords: DISK
  • io/io_submit.stp - Tally Reschedule Reason During AIO io_submit Call
    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/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.

    • -- cgit From 22f971e83eddada009053d964a397550807b9b50 Mon Sep 17 00:00:00 2001 From: William Cohen Date: Mon, 9 Feb 2009 10:12:00 -0500 Subject: Revised version of kmalloc-top in systemtap.examples. --- 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 17c520ef..5c6e2fdb 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -73,6 +73,9 @@ keywords: IO
  • io/traceio2.stp - Watch I/O Activity on a Particular Device
    keywords: IO

    Print out the executable name and process number as reads and writes to the specified device occur.

    • +
  • memory/kmalloc-top - Show Paths to Kernel Malloc (kmalloc) Invocations
    +keywords: MEMORY
    +

    The kmalloc-top perl program runs a small systemtap script to collect stack traces for each call to the kmalloc function and counts the time that each stack trace is observed. When kmalloc-top exits it prints out sorted list. The output can be be filtered to print only only the first stack traces (-t) stack traces with more a minimum counts (-m), or exclude certain stack traces (-e).

  • 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 413996e0c3b55047e12272678627f7833228d892 Mon Sep 17 00:00:00 2001 From: William Cohen Date: Thu, 12 Feb 2009 15:58:24 -0500 Subject: Function to determine page fault type and have pfaults.stp exercise it. --- 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 5c6e2fdb..7b76baa1 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -76,6 +76,9 @@ keywords: IO
  • memory/kmalloc-top - Show Paths to Kernel Malloc (kmalloc) Invocations
    keywords: MEMORY

    The kmalloc-top perl program runs a small systemtap script to collect stack traces for each call to the kmalloc function and counts the time that each stack trace is observed. When kmalloc-top exits it prints out sorted list. The output can be be filtered to print only only the first stack traces (-t) stack traces with more a minimum counts (-m), or exclude certain stack traces (-e).

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

  • 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