From 1ff1a65d89bf66a877a1685e96d20a2a1379cece Mon Sep 17 00:00:00 2001 From: "Frank Ch. Eigler" Date: Tue, 12 Jan 2010 11:49:48 -0500 Subject: new sample script: overcommit failure monitor --- 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 5c226901..5b4ef659 100644 --- a/testsuite/systemtap.examples/index.html +++ b/testsuite/systemtap.examples/index.html @@ -121,6 +121,9 @@ keywords: MEMORY
  • 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 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/overcommit.stp - Log failed process memory allocation due to overcommit limits
    +keywords: MEMORY PROCESS
    +

    The overcommit.stp script prints a line each time the kernel refuses a memory allocation request from a process because of /proc/sys/vm/overcommit* limits.

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

    • -- cgit