public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Christoph Hellwig <hch@infradead.org>,
	eranian@hpl.hp.com, linux-kernel@vger.kernel.org,
	systemtap@sources.redhat.com, wcohen@redhat.com,
	perfmon@napali.hpl.hp.com
Subject: Re: [PATCH 9/16] 2.6.17-rc6 perfmon2 patch for review: kernel-level API support (kapi)
Date: Fri, 16 Jun 2006 12:18:06 -0400	[thread overview]
Message-ID: <20060616161806.GI30867@redhat.com> (raw)
In-Reply-To: <20060616154519.GA28931@infradead.org>

Hi -

> > Whether one uses systemtap, raw kprobes, or some specialized
> > tracing/stats-collecting patch surely forthcoming, kernel-level APIs
> > would be needed to perform fine-grained kernel-scope measurements
> > using these counters.
> 
> No, there's not need to add kernel bloat for performance monitoring.
> This kind of stuff shoul dabsolutely be done from userspace.

Userspace measurements provide only large-grained quantities.  Can you
argue convincingly that there is never a need to measure focused
quantities such as cache behaviors of individual subsystems, branch
prediction statistics of a new algorithm?  That running system-level
benchmarks is the most efficient way for developers to assess their
changes?  That the scheduler would not benefit from access to HT
resource utilization statistics?  All these sorts of efforts seem
to require a kernel-side perfmon API.

- FChE

  reply	other threads:[~2006-06-16 16:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-15  9:07 [PATCH 9/16] 2.6.17-rc6 perfmon2 patch for review: kernel-level API support (kapi) Stephane Eranian
2006-06-16 13:50 ` Christoph Hellwig
2006-06-16 14:02   ` Stephane Eranian
2006-06-16 14:56     ` Christoph Hellwig
2006-06-17  0:15       ` Alan Cox
2006-06-16 15:41     ` Frank Ch. Eigler
2006-06-16 15:45       ` Christoph Hellwig
2006-06-16 16:18         ` Frank Ch. Eigler [this message]
2006-06-22 12:12         ` [perfmon] " Stephane Eranian
2006-06-22 17:00           ` William Cohen

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=20060616161806.GI30867@redhat.com \
    --to=fche@redhat.com \
    --cc=eranian@hpl.hp.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perfmon@napali.hpl.hp.com \
    --cc=systemtap@sources.redhat.com \
    --cc=wcohen@redhat.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