public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: wcohen@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-61-g99f8377 Date: Fri, 02 Mar 2012 17:14:00 -0000 [thread overview] Message-ID: <20120302171447.10135.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 99f837735ae7c4dae0cc296ead455a19c5155422 (commit) via 004a24c569aa42e759b6e453014fc9dbb562ef3e (commit) from 0102305e3573868b852faf5183451676beaedbe6 (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 99f837735ae7c4dae0cc296ead455a19c5155422 Author: William Cohen <wcohen@redhat.com> Date: Fri Mar 2 12:13:53 2012 -0500 Clean out tracking for blocks that are merged into other blocks The IO system in linux often merges blocks together to reduce the number of IO operations sent to IO devices. If nothing is done the tracking for merged IO operations can fill up the associative arrays, causing the script to fail. This problem was reported in rhbz743591. This commit resolves this problem. commit 004a24c569aa42e759b6e453014fc9dbb562ef3e Author: William Cohen <wcohen@redhat.com> Date: Fri Mar 2 12:13:13 2012 -0500 Revert "Clean out tracking for blocks that are merged into other blocks" This reverts commit 0102305e3573868b852faf5183451676beaedbe6. ----------------------------------------------------------------------- Summary of changes: testsuite/systemtap.base/vma_vdso.stp | 2 -- 1 files changed, 0 insertions(+), 2 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-03-02 17:14 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=20120302171447.10135.qmail@sourceware.org \ --to=wcohen@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).