public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Josh Stone <jistone@redhat.com>
To: Aubrey Li <aubreylee@gmail.com>, "Frank Ch. Eigler" <fche@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: kernel function probe overhead
Date: Tue, 29 Nov 2016 19:21:00 -0000	[thread overview]
Message-ID: <9f297ed9-e535-5f4d-e9ee-98507961f3f6@redhat.com> (raw)
In-Reply-To: <CAGPKeULiGUPMQ6e-YjSY3MTW+r=rjxYHYmoKEb1sU4DN+SL1Lg@mail.gmail.com>

On 11/28/2016 07:30 PM, Aubrey Li wrote:
>> Another solution would be to have per-thread global variables.  Since
>> > the kernel doesn't help us out with this, we'd have to emulate it
>> > somehow, and for this to be wortwhile, it'd have to work faster than
>> > ordinary locked/shared array[tid()] accesses.
>> >
> Is this a suggestion for me? How to do this?

There are relevant RFEs for stap already:

per-cpu: https://sourceware.org/bugzilla/show_bug.cgi?id=10795
per-thread: https://sourceware.org/bugzilla/show_bug.cgi?id=10796

The latter was closed on the hunch that it wouldn't help much, but that
could still be explored if someone is interested.

  reply	other threads:[~2016-11-29 19:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-25 16:07 Aubrey Li
2016-11-25 17:22 ` Frank Ch. Eigler
2016-11-26  6:18   ` Aubrey Li
2016-11-28 19:19     ` Frank Ch. Eigler
2016-11-29  3:31       ` Aubrey Li
2016-11-29 19:21         ` Josh Stone [this message]
2016-12-01 18:47         ` Cody Santing
     [not found]           ` <CAGPKeUKm9EZZxL=MHZX9_0N5SUYX291mJMTCExYSspRceJgrxg@mail.gmail.com>
2016-12-12 17:07             ` Fwd: " Cody Santing
2016-12-12 17:43               ` Frank Ch. Eigler

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=9f297ed9-e535-5f4d-e9ee-98507961f3f6@redhat.com \
    --to=jistone@redhat.com \
    --cc=aubreylee@gmail.com \
    --cc=fche@redhat.com \
    --cc=systemtap@sourceware.org \
    /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).