From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 2303 invoked by alias); 12 May 2010 13:08:00 -0000 Received: (qmail 2242 invoked by uid 48); 12 May 2010 13:07:48 -0000 Date: Wed, 12 May 2010 17:16:00 -0000 From: "fche at redhat dot com" To: systemtap@sources.redhat.com Message-ID: <20100512130744.11592.fche@redhat.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug runtime/11592] New: sdt.h should have a 'disable-semaphores' override option 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: 2010-q2/txt/msg00322.txt.bz2 See https://bugzilla.gnome.org/show_bug.cgi?id=606044 for a situation where semaphores constitute a performance regression. (In this case, argument setup is small compared to the semaphore value check.) Unless we can automate per-marker semaphore presence, we should provide an override capability. It may need to be nothing larger than allowing an application .c file to define #define STAP_NO_SEMAPHORES which then the dtrace.in-generated script would observe and avoid defining STAP_HAS_SEMAPHORES. -- Summary: sdt.h should have a 'disable-semaphores' override option Product: systemtap Version: unspecified Status: NEW Severity: normal Priority: P2 Component: runtime AssignedTo: systemtap at sources dot redhat dot com ReportedBy: fche at redhat dot com CC: scox at redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=11592 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.