public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/11592] New: sdt.h should have a 'disable-semaphores' override option
Date: Wed, 12 May 2010 17:16:00 -0000	[thread overview]
Message-ID: <20100512130744.11592.fche@redhat.com> (raw)

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.

             reply	other threads:[~2010-05-12 13:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-12 17:16 fche at redhat dot com [this message]
2010-05-12 17:43 ` [Bug runtime/11592] " alexl at redhat dot com
2010-05-12 17:48 ` fche at redhat dot com
2010-05-14 19:44 ` alexl at redhat dot com
2010-05-25 15:11 ` walters at verbum dot org
2010-05-25 15:20 ` fche at redhat dot com
2010-05-26  1:31 ` alexl at redhat dot com
2010-05-27 14:19 ` scox 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=20100512130744.11592.fche@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).