From: "jistone at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10796] New: thread-specific globals
Date: Fri, 16 Oct 2009 22:23:00 -0000 [thread overview]
Message-ID: <20091016222303.10796.jistone@redhat.com> (raw)
Similar to PR10795, it would also be nice to have native per-thread globals.
It's a common pattern to have maps indexed only by tid(), so it would be nice if
that were automatic and lockless.
Per-thread is not as easy as per-cpu though -- we'll probably need to have a
fixed pool of thread storage areas, allocating when a probe hits a thread,
deallocating when a thread dies (perhaps even on exec). Those lookups might
need some locking, but hopefully that could be more fine-grained than wrapping
the entire probe.
--
Summary: thread-specific globals
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=10796
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2009-10-16 22:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-16 22:23 jistone at redhat dot com [this message]
2009-10-23 23:42 ` [Bug translator/10796] " jistone at redhat dot com
2009-10-26 16:03 ` jkenisto at us dot ibm 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=20091016222303.10796.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).