From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: Jiri Olsa <jolsa@kernel.org>, lkml <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Michael Petlan <mpetlan@redhat.com>
Subject: Re: [PATCH 1/3] perf tools: Allow to build with -ltcmalloc
Date: Mon, 14 Oct 2019 11:01:37 -0300 [thread overview]
Message-ID: <20191014140137.GA19627@kernel.org> (raw)
In-Reply-To: <20191014013322.GI9933@tassilo.jf.intel.com>
Em Sun, Oct 13, 2019 at 06:33:22PM -0700, Andi Kleen escreveu:
> > diff --git a/tools/perf/Makefile.perf b/tools/perf/Makefile.perf
> > index a099a8a89447..8f1ba986d3bf 100644
> > --- a/tools/perf/Makefile.perf
> > +++ b/tools/perf/Makefile.perf
> > @@ -114,6 +114,8 @@ include ../scripts/utilities.mak
> > # Define NO_LIBZSTD if you do not want support of Zstandard based runtime
> > # trace compression in record mode.
> > #
> > +# Define TCMALLOC to enable tcmalloc heap profiling.
>
> It might be useful for more than just profiling. I found that gcc runs a
> few percent faster with tcmalloc for some workloads. Maybe the same is
> true for perf too, as sometimes it does a lot of mallocs.
Thanks, applied. Waiting for the conclusion of the discussion about JIT,
etc to look at the rest.
- Arnaldo
next prev parent reply other threads:[~2019-10-14 14:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-13 15:14 [PATCH 0/3] perf tools: Share struct map after clone Jiri Olsa
2019-10-13 15:14 ` [PATCH 1/3] perf tools: Allow to build with -ltcmalloc Jiri Olsa
2019-10-14 1:33 ` Andi Kleen
2019-10-14 14:01 ` Arnaldo Carvalho de Melo [this message]
2019-10-21 23:19 ` [tip: perf/core] " tip-bot2 for Jiri Olsa
2019-10-13 15:14 ` [PATCH 2/3] perf tools: Separate shareable part of 'struct map' into 'struct map_shared' Jiri Olsa
2019-10-13 15:14 ` [PATCH 3/3] perf tools: Make 'struct map_shared' truly shared Jiri Olsa
2019-10-14 3:10 ` Andi Kleen
2019-10-14 8:48 ` Jiri Olsa
2019-10-14 19:20 ` Jiri Olsa
2019-10-14 19:46 ` Andi Kleen
2019-10-14 20:40 ` Jiri Olsa
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=20191014140137.GA19627@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.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.