From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Pierre Tardy <tardyp@gmail.com>, Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Tom Zanussi <tzanussi@gmail.com>,
Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org, arjan@infradead.org,
ziga.mahkovec@gmail.com, davem <davem@davemloft.net>
Subject: Re: Perf and ftrace [was Re: PyTimechart]
Date: Wed, 12 May 2010 13:07:34 -0400 [thread overview]
Message-ID: <20100512170734.GA15953@Krystal> (raw)
In-Reply-To: <1273683624.1626.127.camel@laptop>
* Peter Zijlstra (peterz@infradead.org) wrote:
> On Wed, 2010-05-12 at 18:46 +0200, Frederic Weisbecker wrote:
> > But there is no strong reason for perf record not to use splice,
> > a part the fact that perf doesn't support splice.
> >
> Its mostly an interface/api question. You cannot easily splice() a
> mmap()'ed buffer on machines that have address constraints like sparc.
Ah ? Can you explain this issue a bit more ? There is possibly a concern I don't
quite see here.
Thanks,
Mathieu
>
> The thing I was thinking about is adding a new syscall that creates a
> single buffer of specified size and provides a fd. Then use
> PERF_EVENT_IOC_SET_OUTPUT, to connect an event to that fd/buffer and use
> splice() on that fd.
>
> It could reuse most of the perf buffer code, but simply not map it into
> userspace and therefore not have the restriction on the vaddr.
>
> Once you have that, a .splice_read implementation shouldn't be too hard.
>
--
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2010-05-12 17:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 21:10 [RFC] PyTimechart Pierre Tardy
2010-05-11 21:36 ` Frederic Weisbecker
2010-05-12 13:37 ` Pierre Tardy
2010-05-12 14:48 ` Frederic Weisbecker
2010-05-12 15:36 ` Steven Rostedt
2010-05-12 16:46 ` Perf and ftrace [was Re: PyTimechart] Frederic Weisbecker
2010-05-12 17:00 ` Peter Zijlstra
2010-05-12 17:07 ` Mathieu Desnoyers [this message]
2010-05-12 17:47 ` Peter Zijlstra
2010-05-12 17:53 ` Mathieu Desnoyers
2010-05-12 18:00 ` Peter Zijlstra
2010-05-12 18:04 ` Mathieu Desnoyers
2010-05-12 18:08 ` Peter Zijlstra
2010-05-12 18:37 ` Mathieu Desnoyers
2010-05-12 18:46 ` Steven Rostedt
2010-05-12 20:27 ` Mathieu Desnoyers
2010-05-12 22:21 ` Steven Rostedt
2010-05-13 13:20 ` Mathieu Desnoyers
2010-05-13 15:42 ` Steven Rostedt
2010-05-13 16:31 ` Mathieu Desnoyers
2010-05-13 16:46 ` Steven Rostedt
2010-05-13 17:10 ` Mathieu Desnoyers
2010-05-13 18:33 ` Steven Rostedt
2010-05-14 7:53 ` Peter Zijlstra
2010-05-12 18:49 ` Peter Zijlstra
2010-05-12 18:51 ` Mathieu Desnoyers
2010-05-12 19:01 ` Peter Zijlstra
2010-05-12 20:52 ` Mathieu Desnoyers
2010-05-12 17:11 ` Ingo Molnar
2010-05-12 16:59 ` [RFC] PyTimechart Ingo Molnar
2010-05-12 17:15 ` Steven Rostedt
2010-05-12 18:23 ` Ingo Molnar
2010-05-12 17:13 ` Pierre Tardy
2010-05-13 15:02 ` Arnaldo Carvalho de Melo
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=20100512170734.GA15953@Krystal \
--to=mathieu.desnoyers@efficios.com \
--cc=acme@redhat.com \
--cc=arjan@infradead.org \
--cc=davem@davemloft.net \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tardyp@gmail.com \
--cc=tzanussi@gmail.com \
--cc=ziga.mahkovec@gmail.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;
as well as URLs for NNTP newsgroup(s).