summaryrefslogtreecommitdiffstats
path: root/testsuite/systemtap.examples/memory/mmwriteback.meta
diff options
context:
space:
mode:
authorWilliam Cohen <wcohen@redhat.com>2009-08-31 16:53:40 -0400
committerWilliam Cohen <wcohen@redhat.com>2009-08-31 16:53:40 -0400
commit0dc23d1d3435d0a1b8721618e6c898b9216a27e2 (patch)
tree45073bf69363dc8f0517561dacde002d4f18e19c /testsuite/systemtap.examples/memory/mmwriteback.meta
parentd97876c8cd8488865753fa6a6055ab3a58d7219a (diff)
downloadsystemtap-steved-0dc23d1d3435d0a1b8721618e6c898b9216a27e2.tar.gz
systemtap-steved-0dc23d1d3435d0a1b8721618e6c898b9216a27e2.tar.xz
systemtap-steved-0dc23d1d3435d0a1b8721618e6c898b9216a27e2.zip
Add virtual memory subsystem tracepoint examples.
Diffstat (limited to 'testsuite/systemtap.examples/memory/mmwriteback.meta')
-rw-r--r--testsuite/systemtap.examples/memory/mmwriteback.meta13
1 files changed, 13 insertions, 0 deletions
diff --git a/testsuite/systemtap.examples/memory/mmwriteback.meta b/testsuite/systemtap.examples/memory/mmwriteback.meta
new file mode 100644
index 00000000..aab0f910
--- /dev/null
+++ b/testsuite/systemtap.examples/memory/mmwriteback.meta
@@ -0,0 +1,13 @@
+title: Track Virtual Memory System Writing to Disk
+name: mmwriteback.stp
+version: 1.0
+author: Red Hat
+keywords: memory
+subsystem: memory
+status: experimental
+exit: user-controlled
+output: sorted-list
+scope: system-wide
+description: 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.
+test_check: stap -p4 mmwriteback.stp
+test_installcheck: stap mmwriteback.stp -c "sleep 1"