From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Andi Kleen <andi@firstfloor.org>
Cc: Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
Namhyung Kim <namhyung.kim@lge.com>,
LKML <linux-kernel@vger.kernel.org>,
David Ahern <dsahern@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Milian Wolff <mail@milianw.de>
Subject: Re: [PATCH v2 2/2] perf record: Show precise number of samples
Date: Fri, 28 Nov 2014 18:48:40 -0300 [thread overview]
Message-ID: <20141128214840.GL30226@kernel.org> (raw)
In-Reply-To: <20141128175613.GY12538@two.firstfloor.org>
Em Fri, Nov 28, 2014 at 06:56:13PM +0100, Andi Kleen escreveu:
> > > Reported-by: Milian Wolff <mail@milianw.de>
> > > Signed-off-by: Namhyung Kim <namhyung@kernel.org>
> >
> > eeeey great, I mean.. finally ;-)
>
> Yes I like it too.
>
> BTW it would be nice if we could show down a break down on how many
> bytes the different options passed to perf record added, by accounting
> the different header fields. That would guide people who suffer
> from too large perf.data files.
That is a good idea, after perf_evsel__parse_sample() we add up the
things that are variable: callchains, branch_stack, etc.
Will implement if nobody does it first :-)
- Arnaldo
prev parent reply other threads:[~2014-11-28 21:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 7:11 [PATCH 1/2] perf tools: Do not use __perf_session__process_events() directly Namhyung Kim
2014-11-28 7:11 ` [PATCH 2/2] perf record: Show precise number of samples Namhyung Kim
2014-11-28 7:14 ` [PATCH v2 " Namhyung Kim
2014-11-28 12:44 ` Jiri Olsa
2014-11-28 17:56 ` Andi Kleen
2014-11-28 21:48 ` Arnaldo Carvalho de Melo [this message]
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=20141128214840.GL30226@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=adrian.hunter@intel.com \
--cc=andi@firstfloor.org \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@milianw.de \
--cc=mingo@kernel.org \
--cc=namhyung.kim@lge.com \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.