From: fche@redhat.com (Frank Ch. Eigler)
To: Nathan Scott <nathans@redhat.com>
Cc: David Smith <dsmith@redhat.com>,
pcp@oss.sgi.com, Systemtap List <systemtap@sourceware.org>
Subject: Re: systemtap/pcp integration
Date: Tue, 22 Jul 2014 02:57:00 -0000 [thread overview]
Message-ID: <y0mlhrmw160.fsf@fche.csb> (raw)
In-Reply-To: <861139755.14608867.1405992742567.JavaMail.zimbra@redhat.com> (Nathan Scott's message of "Mon, 21 Jul 2014 21:32:22 -0400 (EDT)")
Hi, Nathan -
nathans wrote:
> [...]
> (OOC, what's {MODULE_NAME} in this context?)
It is usually a machine-generated unique identifier for the systemtap
script in question, such as "stap_deadbeefdeadbeefdeadbeef_2222". It
is not generally predictable in advance. (A user can override the
name, but that costs possible collisions.)
> [...] PMDA is written to be able to detect arrival/departure of new
> MMV files based on changes in a directory (and the location of that
> directory is parameterised via /etc/pcp.conf variables). [...]
If we do end up sticking with this MMV approach, the PMDA would
probably need to use glob(3) or similar to search for
"/proc/systemtap/*/mmv" instead of "/proc/mmv/*".
> It also occurs to me that there's not really anything
> systemtap-specific about the kernel MMV instrumentation you've done,
> or is there? [...] It would be worth thinking about if the MMV
> bits in your script could become a more general kernel module for
> others to use too [...]
Yes, perhaps, though the path of code implementing a seemingly good
idea into the kernel is rarely smooth. They generally dislike
infrastructure unless it's well-yearned-for. So, if you wish to
pursue this goal, some serious selling on LKML will be needed.
- FChE
next prev parent reply other threads:[~2014-07-22 2:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 21:14 David Smith
2014-07-18 15:49 ` Frank Ch. Eigler
2014-07-18 17:02 ` David Smith
2014-07-18 18:27 ` Frank Ch. Eigler
2014-07-22 14:25 ` David Smith
2014-07-22 15:21 ` Frank Ch. Eigler
2014-07-22 21:02 ` David Smith
2014-07-18 21:10 ` [pcp] " William Cohen
2014-07-21 15:43 ` David Smith
2014-07-21 15:54 ` William Cohen
2014-07-22 1:32 ` Nathan Scott
2014-07-22 2:57 ` Frank Ch. Eigler [this message]
2014-07-22 14:50 ` David Smith
2014-07-23 10:29 ` Nathan Scott
2014-07-23 14:42 ` Frank Ch. Eigler
2014-07-24 7:40 ` Nathan Scott
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=y0mlhrmw160.fsf@fche.csb \
--to=fche@redhat.com \
--cc=dsmith@redhat.com \
--cc=nathans@redhat.com \
--cc=pcp@oss.sgi.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).