public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
	David Sharp <dhsharp@google.com>,
	Vaibhav Nagarnaik <vnagarnaik@google.com>,
	Paul Menage <menage@google.com>, Li Zefan <lizf@cn.fujitsu.com>,
	Stephane Eranian <eranian@google.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Michael Rubin <mrubin@google.com>, Ken Chen <kenchen@google.com>,
	linux-kernel@vger.kernel.org,
	containers@lists.linux-foundation.org,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [RFC] tracing: Adding cgroup aware tracing functionality
Date: Fri, 08 Apr 2011 16:07:50 +0200	[thread overview]
Message-ID: <1302271670.9086.154.camel@twins> (raw)
In-Reply-To: <1302248268.21026.18.camel@frodo>

On Fri, 2011-04-08 at 03:37 -0400, Steven Rostedt wrote:
> I don't think this is about perf and ftrace as competitors, but they are
> currently two different infrastructures that are existing in the kernel.
> They are currently optimized for different purposes. ftrace is optimized
> for system tracing (persistent buffers and such) where as perf is
> optimized for user tracing. 

That's complete nonsense, perf isn't build for tracing at all, its just
that tracing is a special case of the larger problem set of
sampling/profiling it is build for.

Nor is perf in any way shape or form better suited for user than for
kernel space, it really doesn't care, if we'd only be interested in user
crap we'd never have done NMI sampling for instance.

> But the two can do both but the other
> feature is not as efficient as the other tool.

Well, neither can do user-space-tracing at all, simply because we don't
have hooks into userspace, although the uprobes stuff looks to cure some
of that.

> As you said perf has a lot of overhead due to data that it saves per
> event. 

Someday you should actually read the perf code before you say something.


  parent reply	other threads:[~2011-04-08 14:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-06 18:50 [RFC] tracing: Adding cgroup aware tracing functionality Vaibhav Nagarnaik
2011-04-07  1:33 ` Frederic Weisbecker
2011-04-07  3:17   ` Vaibhav Nagarnaik
2011-04-07 12:06     ` Frederic Weisbecker
2011-04-07 20:22       ` David Sharp
2011-04-07 21:32         ` Frederic Weisbecker
2011-04-07 22:42           ` David Sharp
2011-04-08  0:28             ` Frederic Weisbecker
2011-04-08  7:37               ` Steven Rostedt
2011-04-08 13:45                 ` Frederic Weisbecker
2011-04-08 14:07                   ` Peter Zijlstra
2011-04-08 18:32                     ` Michael Rubin
2011-04-08 20:27                       ` Justin TerAvest
2011-04-08 14:07                 ` Peter Zijlstra [this message]
2011-04-08 17:02                   ` Steven Rostedt
2011-04-09 11:08                     ` Peter Zijlstra
2011-04-08 19:00                 ` Frederic Weisbecker
2011-04-08 20:38                   ` Frederic Weisbecker
2011-04-08 21:41                     ` David Sharp
2011-04-12 21:38                       ` Frederic Weisbecker

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=1302271670.9086.154.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=dhsharp@google.com \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=kenchen@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizf@cn.fujitsu.com \
    --cc=menage@google.com \
    --cc=mingo@elte.hu \
    --cc=mrubin@google.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=vnagarnaik@google.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