From: "Frank Ch. Eigler" <fche@redhat.com>
To: Andi Kleen <ak@suse.de>
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 14:28:08 -0400 [thread overview]
Message-ID: <20060517182808.GL17707@redhat.com> (raw)
In-Reply-To: <200605172005.44588.ak@suse.de>
Hi -
On Wed, May 17, 2006 at 08:05:43PM +0200, Andi Kleen wrote:
> [...]
> > 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.
I am not suggesting a single solution for all needs. I wanted to
focus only one aspect: the marking of those points in the kernel where
something probeworthy occurs with hooks. The different tools would
still gather and disseminate their data in their own favorite. The
main difference from the status quo is agreeing on and reusing a
common pool of hooks.
- FChE
next prev parent reply other threads:[~2006-05-17 18:28 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
2006-05-17 18:05 ` Andi Kleen
2006-05-17 18:28 ` Frank Ch. Eigler [this message]
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=20060517182808.GL17707@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.