From: Namhyung Kim <namhyung@kernel.org>
To: Arnaldo Carvalho de Melo <acme@kernel.org>, Jiri Olsa <jolsa@kernel.org>
Cc: Ian Rogers <irogers@google.com>,
Adrian Hunter <adrian.hunter@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-perf-users@vger.kernel.org
Subject: [PATCHSET 0/5] perf annotate: Reduce memory footprint (v1)
Date: Thu, 2 Nov 2023 15:26:48 -0700 [thread overview]
Message-ID: <20231102222653.4165959-1-namhyung@kernel.org> (raw)
Hello,
This is a part of my work to improve perf annotate. At first, I'd
like reduce the size of struct annotation which will be allocated
together with struct symbol in some cases. In fact, it doesn't use
most of them so it needs to slim down and lazy-allocate used part.
With this applied, size of the struct goes down from 96 to 48.
The code is available at perf/annotate-diet-v1 branch in
git://git.kernel.org/pub/scm/linux/kernel/git/namhyung/linux-perf.git
Thanks,
Namhyung
Namhyung Kim (5):
perf annotate: Split struct cycles_info
perf annotate: Split struct annotated_branch
perf annotate: Move max_coverage to annotated_branch
perf annotate: Move some fields to annotated_source
perf annotate: Move offsets to annotated_source
tools/perf/builtin-annotate.c | 7 +-
tools/perf/ui/browsers/annotate.c | 18 ++--
tools/perf/util/annotate.c | 162 ++++++++++++++++--------------
tools/perf/util/annotate.h | 49 +++++----
tools/perf/util/block-info.c | 4 +-
tools/perf/util/block-range.c | 7 +-
tools/perf/util/sort.c | 14 +--
7 files changed, 147 insertions(+), 114 deletions(-)
--
2.42.0.869.gea05f2083d-goog
next reply other threads:[~2023-11-02 22:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 22:26 Namhyung Kim [this message]
2023-11-02 22:26 ` [PATCH 1/5] perf annotate: Split struct cycles_info Namhyung Kim
2023-11-02 22:52 ` Ian Rogers
2023-11-03 18:48 ` Namhyung Kim
2023-11-02 22:26 ` [PATCH 2/5] perf annotate: Split struct annotated_branch Namhyung Kim
2023-11-02 22:58 ` Ian Rogers
2023-11-03 18:49 ` Namhyung Kim
2023-11-02 22:26 ` [PATCH 3/5] perf annotate: Move max_coverage to annotated_branch Namhyung Kim
2023-11-02 22:59 ` Ian Rogers
2023-11-02 22:26 ` [PATCH 4/5] perf annotate: Move some fields to annotated_source Namhyung Kim
2023-11-02 23:00 ` Ian Rogers
2023-11-03 5:41 ` Christophe JAILLET
2023-11-03 18:58 ` Namhyung Kim
2023-11-02 22:26 ` [PATCH 5/5] perf annotate: Move offsets " Namhyung Kim
2023-11-02 23:00 ` Ian Rogers
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=20231102222653.4165959-1-namhyung@kernel.org \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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;
as well as URLs for NNTP newsgroup(s).