All of lore.kernel.org
 help / color / mirror / Atom feed
From: fche@redhat.com (Frank Ch. Eigler)
To: Martin Peschke <mp3@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org, ak@suse.de,
	hch@infradead.org, arjan@infradead.org, James.Smart@Emulex.Com,
	James.Bottomley@SteelEye.com, ltt-dev@shafik.org
Subject: Re: [RFC] [Patch 0/8] statistics infrastructure
Date: 17 May 2006 13:23:19 -0400	[thread overview]
Message-ID: <y0msln8wooo.fsf@ton.toronto.redhat.com> (raw)
In-Reply-To: <446A0F77.70202@de.ibm.com>


Martin Peschke <mp3@de.ibm.com> writes:

> My patch series is a proposal for a generic implementation of statistics.
> Envisioned exploiters include device drivers, and any other component.
> [...]
> Good places to start reading code are:
>    statistic_create(), statistic_remove()
>    statistic_add(), statistic_inc()
> [...]

It is interesting how many solutions pop up for this sort of problem.
The many tracing tools/patches, systemtap, and now this, all share
some goals and should ideally share some of the technology.

In particular, one of the common points is the designation of points
where significant events take place, and passing their parameters.  In
your case, these are the statitistic_add/inc() calls.  In LTT, these
are macros or inline functions expanding to tracing calls.  In
systemtap, ignoring the slower dynamic kprobes, we now have prototype
support for "markers" are generic statically placed hooks that may be
bound to arbitrary instrumentation code.  (I will be talking more
about this at OLS.)
<http://sourceware.org/ml/systemtap/2006-q1/msg00901.html>

It would be nice if we found a way to agree on one single hooking
mechanism, one that could be accepted here upstream, and used by all
these various projects for their own tracing, probing, or
statistics-collecting backends.

- FChE

  reply	other threads:[~2006-05-17 17:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 17:44 [RFC] [Patch 0/8] statistics infrastructure Martin Peschke
2006-05-17 17:23 ` Frank Ch. Eigler [this message]
2006-05-17 18:05   ` Andi Kleen
2006-05-17 18:28     ` Frank Ch. Eigler
2006-05-17 18:44       ` Valdis.Kletnieks
2006-05-17 18:55         ` 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=y0msln8wooo.fsf@ton.toronto.redhat.com \
    --to=fche@redhat.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=James.Smart@Emulex.Com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@shafik.org \
    --cc=mp3@de.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.