From: David Ahern <dsahern@gmail.com>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Ingo Molnar <mingo@elte.hu>, Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Stephane Eranian <eranian@google.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 0/4] perf tools: New comm infrastructure
Date: Fri, 13 Sep 2013 08:59:02 -0700 [thread overview]
Message-ID: <52333646.1020103@gmail.com> (raw)
In-Reply-To: <20130913124354.GB4844@somewhere>
On 9/13/13 5:43 AM, Frederic Weisbecker wrote:
> The only way would be perhaps to be able to limit the deepness
> of the callchain branches.
I was thinking about such a feature two days ago. Max callchain depth is
set to 255 at compile time which can generate huge event sizes. perf
needs to allow the user to specify max depth for an event at less than that.
David
next prev parent reply other threads:[~2013-09-14 20:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 20:29 [PATCH 0/4] perf tools: New comm infrastructure Frederic Weisbecker
2013-09-12 20:29 ` [PATCH 1/4] perf tools: Use an accessor to read thread comm Frederic Weisbecker
2013-09-12 20:29 ` [PATCH 2/4] perf tools: Add time argument on comm setting Frederic Weisbecker
2013-09-12 20:29 ` [PATCH 3/4] perf tools: Add new comm infrastructure Frederic Weisbecker
2013-09-12 20:29 ` [PATCH 4/4] perf tools: Compare hists comm by addresses Frederic Weisbecker
2013-09-13 8:07 ` Namhyung Kim
2013-09-13 13:59 ` Frederic Weisbecker
2013-09-17 1:46 ` Namhyung Kim
2013-09-12 20:36 ` [PATCH 0/4] perf tools: New comm infrastructure Ingo Molnar
2013-09-13 12:43 ` Frederic Weisbecker
2013-09-13 15:59 ` David Ahern [this message]
2013-09-14 6:11 ` Ingo Molnar
2013-09-17 5:54 ` Namhyung Kim
2013-09-17 7:16 ` Ingo Molnar
2013-09-18 14:20 ` Arnaldo Carvalho de Melo
2013-09-18 15:12 ` Arnaldo Carvalho de Melo
2013-09-18 15:58 ` Arnaldo Carvalho de Melo
2013-09-18 16:17 ` Namhyung Kim
2013-09-13 6:32 ` Namhyung Kim
2013-09-13 12:46 ` 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=52333646.1020103@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=torvalds@linux-foundation.org \
/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