This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: Systemtap caching behavior
- From: Mark Wielaard <mark at klomp dot org>
- To: Mikhail Zhukovskiy <mikhail dot zhukovskiy at oracle dot com>
- Cc: systemtap at sourceware dot org
- Date: Sun, 13 Jan 2019 10:58:44 +0100
- Subject: Re: Systemtap caching behavior
- References: <58A9823A-4D8B-4948-B14C-74BF25357A3A@oracle.com>
On Sat, Jan 12, 2019 at 07:59:14PM -0500, Mikhail Zhukovskiy wrote:
> I have a question about systemtap caching behavior.
>
> According to the man page, the results of pass 3 and pass 4 (the translation to C and the compilation of the kernel module) should be cached between runs, however this is not what I am observing. Could you please point out what I’m doing wrong?
> [...]
> /home/vagrant/systemtapbin/bin/stap -k -s 32 --all-modules -v -D MAXBACKTRACE=100 -D MAXSTRINGLEN=4096 -D MAXMAPENTRIES=10240 -D DMAXACTION_INTERRUPTIBLE=500 -D MAXACTION=100000 -D STP_OVERLOAD_THRESHOLD=5000000000LL flame-kernel.stp > out.stap-stacks
You are using -k:
-k Keep the temporary directory after all processing. This may be
useful in order to examine the generated C code, or to reuse the
compiled kernel object.
> Keeping temporary directory "/tmp/stapy6Mjkr"
This bypasses the cache.
Cheers,
Mark