public inbox for systemtap-cvs@sourceware.org help / color / mirror / Atom feed
From: fche@sourceware.org To: systemtap-cvs@sourceware.org Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-330-ge04e95a Date: Wed, 19 Oct 2011 03:42:00 -0000 [thread overview] Message-ID: <20111019034255.32514.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 e04e95a488397d0fbf2740c3cfef989b56d7f80a (commit) from 75ab1a70d36a435b6c75565eb4dd3406e4d0ae8c (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 e04e95a488397d0fbf2740c3cfef989b56d7f80a Author: Frank Ch. Eigler <fche@redhat.com> Date: Tue Oct 18 22:49:35 2011 -0400 PR13319: fix _stp_bufsize-related start-time net/ memory report printk * transport/relay_v2.c, relayfs.c (_stp_transport_data_fs_init): Increment _stp_allocated_[net_]memory with relay buffers. * transport/ring_buffer.c: Ditto. Plus fix scaling of the incoming -sNN value, so NN represents megabytes consistently. ----------------------------------------------------------------------- Summary of changes: runtime/transport/relay_v2.c | 12 ++++++++++++ runtime/transport/relayfs.c | 9 +++++++++ runtime/transport/ring_buffer.c | 19 ++++++++++++++++++- 3 files changed, 39 insertions(+), 1 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-10-19 3:42 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=20111019034255.32514.qmail@sourceware.org \ --to=fche@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).