[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100512165947.GA11921@elte.hu>
Date: Wed, 12 May 2010 18:59:47 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
Pierre Tardy <tardyp@...il.com>,
Arnaldo Carvalho de Melo <acme@...hat.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Tom Zanussi <tzanussi@...il.com>,
Paul Mackerras <paulus@...ba.org>,
linux-kernel@...r.kernel.org, mathieu.desnoyers@...icios.com,
arjan@...radead.org, ziga.mahkovec@...il.com
Subject: Re: [RFC] PyTimechart
* Steven Rostedt <rostedt@...dmis.org> wrote:
> On Wed, 2010-05-12 at 16:48 +0200, Frederic Weisbecker wrote:
> > On Wed, May 12, 2010 at 03:37:27PM +0200, Pierre Tardy wrote:
>
> > But we don't yet support trace_printk in perf. May be we could wrap
> > them in trace events.
>
> Hmm, do we really want to do that?
>
> We really need to get the perf and ftrace trace buffers combined. I
> understand why perf chose to do the mmap buffers for the counting, but for
> live streaming, it is very inefficient compared to splice.
The thing is that for a very long time ftrace didnt have splice support and
survived just fine. Even today most of the ftrace usage isnt utilizing splice.
Yes, splice might help in some situations but on average it's an independent
speedup on the order of magnitude of a few percents, not a 'must have' item.
So please keep these issues separate.
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists