From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25086 invoked by alias); 16 Oct 2009 22:23:16 -0000 Received: (qmail 25055 invoked by uid 48); 16 Oct 2009 22:23:03 -0000 Date: Fri, 16 Oct 2009 22:23:00 -0000 From: "jistone at redhat dot com" To: systemtap@sources.redhat.com Message-ID: <20091016222303.10796.jistone@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug translator/10796] New: thread-specific globals X-Bugzilla-Reason: AssignedTo Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2009-q4/txt/msg00181.txt.bz2 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.