summaryrefslogtreecommitdiffstats
path: root/testsuite/systemtap.examples/keyword-index.txt
diff options
context:
space:
mode:
Diffstat (limited to 'testsuite/systemtap.examples/keyword-index.txt')
-rw-r--r--testsuite/systemtap.examples/keyword-index.txt35
1 files changed, 35 insertions, 0 deletions
diff --git a/testsuite/systemtap.examples/keyword-index.txt b/testsuite/systemtap.examples/keyword-index.txt
index a940ccfa..5679474f 100644
--- a/testsuite/systemtap.examples/keyword-index.txt
+++ b/testsuite/systemtap.examples/keyword-index.txt
@@ -125,6 +125,17 @@ keywords: io backtrace
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
@@ -182,6 +193,19 @@ keywords: syscall locking futex
highest.
+= MEMORY =
+
+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 =
network/nettop.stp - Periodic Listing of Processes Using Network Interfaces
@@ -227,6 +251,17 @@ keywords: network traffic per-process
= PROFILING =
+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.
+
+
process/pf2.stp - Profile kernel functions
keywords: profiling