Bug 11246 - Add better control over caching
Summary: Add better control over caching
Status: RESOLVED FIXED
Alias: None
Product: systemtap
Classification: Unclassified
Component: translator (show other bugs)
Version: unspecified
: P2 enhancement
Target Milestone: ---
Assignee: Josh Stone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-03 23:48 UTC by Josh Stone
Modified: 2010-03-03 00:15 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Stone 2010-02-03 23:48:46 UTC
We now have several things that are stored in cache:

1. The script's module, stap.c and stap.ko
2. The common autoconf result, stapconf.h
3. The tracepoint query modules, tracequery.ko
4. The @cast w/ header modules, typequery_umod.so and typequery_kmod.ko

We have a single session variable, use_cache, which controls all of these.  When
someone uses the -k or -m options, we end up disabling all of the cache.  We
really only need to disable #1 in that case, and it would be nice to still
benefit from the rest of the caching.

While we're at it, we could use some command-line options to control the cache
for debugging.  A few ideas:
  --disable-cache : turn off all caching
  --clean-cache   : clean up stale entries and then quit
  --poison-cache  : force regeneration of items that would have hit the cache
Comment 1 Josh Stone 2010-03-03 00:15:50 UTC
Pushed commits:

63d530a PR11246: Add more granular cache control
9b3c54b PR11246 cont'd: Separate script/stapconf caching
d105f66 PR11246 cont'd: Add options for cache control