From: Andi Kleen <ak@suse.de>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Martin Peschke <mp3@de.ibm.com>,
linux-kernel@vger.kernel.org, akpm@osdl.org, 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: Wed, 17 May 2006 20:05:43 +0200 [thread overview]
Message-ID: <200605172005.44588.ak@suse.de> (raw)
In-Reply-To: <y0msln8wooo.fsf@ton.toronto.redhat.com>
On Wednesday 17 May 2006 19:23, Frank Ch. Eigler wrote:
>
> 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.
I disagree. They often have very different requirements - and a one-size-fits-all
solution will be likely too heavyweight for most users.
The passing to user space can be unified, but we already have solutions
for that (seq_*, relayfs). But the actual data gathering is better custom
tailored.
-Andi
next prev parent reply other threads:[~2006-05-17 18:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-16 17:44 Martin Peschke
2006-05-17 17:23 ` Frank Ch. Eigler
2006-05-17 18:05 ` Andi Kleen [this message]
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=200605172005.44588.ak@suse.de \
--to=ak@suse.de \
--cc=James.Bottomley@steeleye.com \
--cc=James.Smart@emulex.com \
--cc=akpm@osdl.org \
--cc=arjan@infradead.org \
--cc=fche@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®