summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDavid Smith <dsmith@redhat.com>2010-01-11 13:23:18 -0600
committerDavid Smith <dsmith@redhat.com>2010-01-11 13:23:18 -0600
commit7c268ab89bbdfd5f69cf0447d038af5ed48f8ca9 (patch)
tree45498b5c48332280028e5a3aaa970ef734233fe3
parente9e2c76f32479e2888a1718e60e1fe74be991471 (diff)
downloadsystemtap-steved-7c268ab89bbdfd5f69cf0447d038af5ed48f8ca9.tar.gz
systemtap-steved-7c268ab89bbdfd5f69cf0447d038af5ed48f8ca9.tar.xz
systemtap-steved-7c268ab89bbdfd5f69cf0447d038af5ed48f8ca9.zip
Added STP_MAXMEMORY documentation.
* stap.1.in: Added STP_MAXMEMORY documentation.
-rw-r--r--stap.1.in7
1 files changed, 7 insertions, 0 deletions
diff --git a/stap.1.in b/stap.1.in
index 94833a5f..7c62205b 100644
--- a/stap.1.in
+++ b/stap.1.in
@@ -1117,6 +1117,13 @@ Maximum number of concurrently armed user-space probes (uprobes), default
somewhat larger than the number of user-space probe points named in the script.
This pool needs to be potentialy large because individual uprobe objects (about
64 bytes each) are allocated for each process for each matching script-level probe.
+.TP
+STP_MAXMEMORY
+Maximum amount of memory (in kilobytes) that the systemtap module
+should use, default unlimited. The memory size includes the size of
+the module itself, plus any additional allocations. This only tracks
+direct allocations by the systemtap runtime. This does not track
+indirect allocations (as done by kprobes/uprobes/etc. internals).
.PP
With scripts that contain probes on any interrupt path, it is possible that