From: Cody Santing <csanting@redhat.com>
To: Aubrey Li <aubreylee@gmail.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
Josh Stone <jistone@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: kernel function probe overhead
Date: Thu, 01 Dec 2016 18:47:00 -0000 [thread overview]
Message-ID: <CAO8qvm4vNzmks+dAN5dPf-AXcD9tj2QbrnfqQvF80_jOW_JqzA@mail.gmail.com> (raw)
In-Reply-To: <CAGPKeULiGUPMQ6e-YjSY3MTW+r=rjxYHYmoKEb1sU4DN+SL1Lg@mail.gmail.com>
Hello Aubrey,
>> Ah, I note that we don't track occurrences of lock contention,
>> even though we could. Opened https://sourceware.org/bugzilla/show_bug.cgi?id=20879
>
> okay, thanks, I'll keep an eye on this ticket.
>
I have yet to update the ticket but I have added tracking of lock
contention. The number of lock contention occurrences on global
variables will be printed following the probe hit report from the '-t'
option.
>> That inconsistency dramatic contention or caching or some other source
>> of jitter. Having the variance figure in there would be useful though.
>> Would anyone like to give that a try? (translate.cxx line 2283ish and
>> runtime/linux/common_session_state.h _stp_stat_init area).
>>
I have also added variance to the '-t' option. It is immediately
following min/avg/max of each probe.
>
> If there is a patch delivered against git head, I can apply it and
> paste the output here.
>
You should find the patch there. Give it a shot, if you have any
feedback I would like to hear it.
Thank you,
Cody Santing
next prev parent reply other threads:[~2016-12-01 18:47 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
2016-12-01 18:47 ` Cody Santing [this message]
[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=CAO8qvm4vNzmks+dAN5dPf-AXcD9tj2QbrnfqQvF80_jOW_JqzA@mail.gmail.com \
--to=csanting@redhat.com \
--cc=aubreylee@gmail.com \
--cc=fche@redhat.com \
--cc=jistone@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).