public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: jistone@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-313-g8cc3cc3 Date: Thu, 13 Oct 2011 23:28:00 -0000 [thread overview] Message-ID: <20111013232825.21196.qmail@sourceware.org> (raw) This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "systemtap: system-wide probe/trace tool". The branch, master has been updated via 8cc3cc330cabadc75714ace155c03ac74ea7ea92 (commit) from a09fc5a45fef1aaf1fca5b02574c9d0e4890e96f (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- commit 8cc3cc330cabadc75714ace155c03ac74ea7ea92 Author: Josh Stone <jistone@redhat.com> Date: Thu Oct 13 15:55:24 2011 -0700 Tweak cache logic to group removals by hash value We used to glob the cache for *.ko, *.so, *.h, and *.log, implicitly assuming that this was all that was cached. For the .ko case we also grouped .c and .sgn to be removed all together. But when any new extension came along, the cache cleanup ignored it. Now we glob instead for any file in the cache that looks like is has a hashed name, and we group removals for all files that appear to have the same hash value, regardless of prefix or suffix. This will hopefully make us more robust against future file-caching changes. * cache.cxx (cache_ent_info): Becomes a vector of paths, with no knowledge needed for modules. Use better types for size and mtime. (clean_cache): Use a new glob that looks for hash-like files, with 32 hex digits in a row. Use a regex to find common HASH_LEN substrings in all those filenames. Build the cache_ent_info groups by HASH_LEN, and proceed to delete old entries until below quota. ----------------------------------------------------------------------- Summary of changes: cache.cxx | 223 +++++++++++++++++++++++++------------------------------------ 1 files changed, 90 insertions(+), 133 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-10-13 23:28 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20111013232825.21196.qmail@sourceware.org \ --to=jistone@sourceware.org \ --cc=systemtap-cvs@sourceware.org \ --cc=systemtap@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).