From 0dc23d1d3435d0a1b8721618e6c898b9216a27e2 Mon Sep 17 00:00:00 2001 From: William Cohen Date: Mon, 31 Aug 2009 16:53:40 -0400 Subject: Add virtual memory subsystem tracepoint examples. --- testsuite/systemtap.examples/memory/mmwriteback.meta | 13 +++++++++++++ 1 file changed, 13 insertions(+) create mode 100644 testsuite/systemtap.examples/memory/mmwriteback.meta (limited to 'testsuite/systemtap.examples/memory/mmwriteback.meta') 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" -- cgit