From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10741] New: Merge tandem locks
Date: Tue, 06 Oct 2009 20:20:00 -0000 [thread overview]
Message-ID: <20091006202043.10741.jistone@redhat.com> (raw)
Since we treat probes atomically, and all locks are grabbed at once, we should
be able to merge locks that are used in identical probe sets. For example,
global A, B
probe syscall.* { println(++A * (B += 2)) }
Each probe here will always grab locks for both A and B, so we might as well
have a single AB lock. They need not have identical R/W characteristics to be
joined -- just use W in each case if any of the single locks would have been W.
--
Summary: Merge tandem locks
Product: systemtap
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: jistone at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=10741
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-10-06 20:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 20:20 jistone at redhat dot com [this message]
2009-11-20 19:43 ` [Bug translator/10741] " fche at redhat dot com
2009-11-20 21:25 ` jistone at redhat dot com
2009-11-20 21:28 ` fche at redhat dot com
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=20091006202043.10741.jistone@redhat.com \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.com \
/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: link
Be 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).