This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug translator/10741] Merge tandem locks
- From: "fche at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sources dot redhat dot com
- Date: 20 Nov 2009 21:28:23 -0000
- Subject: [Bug translator/10741] Merge tandem locks
- References: <20091006202043.10741.jistone@redhat.com>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From fche at redhat dot com 2009-11-20 21:28 -------
(In reply to comment #2)
> One concern is that we could lose atomicity this way.
Clearly we must not risk that.
> If two probes share a
> read lock, and one wants to upgrade to write, it could timeout in waiting for
> the other to release.
We could preclude this situation by applying this optimization only
when we can prove that the code between the initial read-lock and
the later read-write-lock is all side-effect-free. That way a timeout
on the read-write lock would be equivalent to an ordinary skip.
--
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.