From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <systemtap-return-13827-listarch-systemtap=sources.redhat.com@sourceware.org>
Received: (qmail 15572 invoked by alias); 6 Oct 2009 20:20:57 -0000
Received: (qmail 15211 invoked by uid 48); 6 Oct 2009 20:20:44 -0000
Date: Tue, 06 Oct 2009 20:20:00 -0000
From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Message-ID: <20091006202043.10741.jistone@redhat.com>
Reply-To: sourceware-bugzilla@sourceware.org
Subject: [Bug translator/10741] New: Merge tandem locks
X-Bugzilla-Reason: AssignedTo
Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <systemtap.sourceware.org>
List-Subscribe: <mailto:systemtap-subscribe@sourceware.org>
List-Post: <mailto:systemtap@sourceware.org>
List-Help: <mailto:systemtap-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: systemtap-owner@sourceware.org
X-SW-Source: 2009-q4/txt/msg00068.txt.bz2

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.