From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10741] Merge tandem locks
Date: Fri, 20 Nov 2009 19:43:00 -0000 [thread overview]
Message-ID: <20091120194333.24011.qmail@sourceware.org> (raw)
In-Reply-To: <20091006202043.10741.jistone@redhat.com>
------- Additional Comments From fche at redhat dot com 2009-11-20 19:43 -------
archiving irc yak on topic:
fche anyway, I was thinking that another locking-related optimization could be
done by escalating read-to-write locks within probe handlers, suchly:
fche global foo probe bar { if (foo) { foo++ } }
fche so the idea would be to initially read-lock foo, and only later upgrade it
to a write-lock
fche the theory being that some / many (??) probes start with some condition
checking, and some (???) of that time, a write does not actually end up happening
jistone hmm
jistone have to think about whether that could induce any lock inversion
fche oh yeah, lots of complications
fche just wanted to brain-dump here FWIW
jistone probe foo { if (++a) ++b } probe bar { if (++b) ++a } global a,b
jistone does the initial read lock solve that? I think it might...
--
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 prev parent reply other threads:[~2009-11-20 19:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 20:20 [Bug translator/10741] New: " jistone at redhat dot com
2009-11-20 19:43 ` fche at redhat dot com [this message]
2009-11-20 21:25 ` [Bug translator/10741] " jistone at redhat dot com
2009-11-20 21:28 ` fche at redhat dot com
[not found] <bug-10741-6586@http.sourceware.org/bugzilla/>
2020-07-23 15:40 ` 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=20091120194333.24011.qmail@sourceware.org \
--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).