This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug dyninst/14571] New: Make stapdyn multithreaded
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 12 Sep 2012 21:03:43 +0000
- Subject: [Bug dyninst/14571] New: Make stapdyn multithreaded
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=14571
Bug #: 14571
Summary: Make stapdyn multithreaded
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: dyninst
AssignedTo: systemtap@sourceware.org
ReportedBy: jistone@redhat.com
Classification: Unclassified
Right now, probe handlers under stapdyn are completely serialized, hacked in by
using stapdyn_big_dumb_lock in the fake preempt_disable(). We should endeavor
to allow simultaneous handlers in different threads.
We don't actually care about preemption in this environment, nor do we have any
control over cpu pinning anyway. (The application might use affinities, but we
can't force that.) Rather, we should allocate things per-thread as much as
possible, and use more intelligent locking when data sharing is necessary.
Obvious things that need threading are the CONTEXT structure, print buffers,
and stats. It may be enough to mark these as __thread storage, but we need to
take care around thread lifetimes, and also how to collect across threads.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.