From: Andrii Nakryiko <andrii.nakryiko@gmail.com>
To: Yonghong Song <yhs@fb.com>
Cc: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>,
dwarves@vger.kernel.org, Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Bill Wendling <morbo@google.com>, bpf <bpf@vger.kernel.org>,
Kernel Team <kernel-team@fb.com>
Subject: Re: [PATCH dwarves 3/3] dwarf_loader: add option to merge more dwarf cu's into one pahole cu
Date: Fri, 26 Mar 2021 16:21:23 -0700 [thread overview]
Message-ID: <CAEf4BzZ=jWb7KuR6yX+3A4zZUbrgHm=AdxcYVoQ358N5zLGFqw@mail.gmail.com> (raw)
In-Reply-To: <20210325065332.3122473-1-yhs@fb.com>
On Wed, Mar 24, 2021 at 11:53 PM Yonghong Song <yhs@fb.com> wrote:
>
> This patch added an option "merge_cus", which will permit
> to merge all debug info cu's into one pahole cu.
> For vmlinux built with clang thin-lto or lto, there exist
> cross cu type references. For example, you could have
> compile unit 1:
> tag 10: type A
> compile unit 2:
> ...
> refer to type A (tag 10 in compile unit 1)
> I only checked a few but have seen type A may be a simple type
> like "unsigned char" or a complex type like an array of base types.
>
> There are two different ways to resolve this issue:
> (1). merge all compile units as one pahole cu so tags/types
> can be resolved easily, or
> (2). try to do on-demand type traversal in other debuginfo cu's
> when we do die_process().
> The method (2) is much more complicated so I picked method (1).
> An option "merge_cus" is added to permit such an operation.
>
> Merging cu's will create a single cu with lots of types, tags
> and functions. For example with clang thin-lto built vmlinux,
> I saw 9M entries in types table, 5.2M in tags table. The
> below are pahole wallclock time for different hashbits:
> command line: time pahole -J --merge_cus vmlinux
> # of hashbits wallclock time in seconds
> 15 460
> 16 255
> 17 131
> 18 97
> 19 75
> 20 69
> 21 64
> 22 62
> 23 58
> 24 64
What were the numbers for different hashbits without --merge_cus?
>
> Note that the number of hashbits 24 makes performance worse
> than 23. The reason could be that 23 hashbits can cover 8M
> buckets (close to 9M for the number of entries in types table).
> Higher number of hash bits allocates more memory and becomes
> less cache efficient compared to 23 hashbits.
>
> This patch picks # of hashbits 21 as the starting value
> and will try to allocate memory based on that, if memory
> allocation fails, we will go with less hashbits until
> we reach hashbits 15 which is the default for
> non merge-cu case.
>
> Signed-off-by: Yonghong Song <yhs@fb.com>
> ---
> dwarf_loader.c | 90 ++++++++++++++++++++++++++++++++++++++++++++++++++
> dwarves.h | 2 ++
> pahole.c | 8 +++++
> 3 files changed, 100 insertions(+)
>
[...]
next prev parent reply other threads:[~2021-03-26 23:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 6:53 [PATCH dwarves 0/3] add option to merge more dwarf cu's into Yonghong Song
2021-03-25 6:53 ` [PATCH dwarves 1/3] dwarf_loader: permits flexible HASHTAGS__BITS Yonghong Song
2021-03-26 23:13 ` Andrii Nakryiko
2021-03-26 23:26 ` Yonghong Song
2021-03-29 14:02 ` Arnaldo Carvalho de Melo
2021-03-31 4:30 ` Andrii Nakryiko
2021-03-25 6:53 ` [PATCH dwarves 2/3] dwarf_loader: factor out common code to initialize a cu Yonghong Song
2021-03-25 6:53 ` [PATCH dwarves 3/3] dwarf_loader: add option to merge more dwarf cu's into one pahole cu Yonghong Song
2021-03-26 14:41 ` Arnaldo Carvalho de Melo
2021-03-26 15:18 ` Yonghong Song
2021-03-26 17:35 ` Arnaldo Carvalho de Melo
2021-03-26 18:19 ` Arnaldo Carvalho de Melo
2021-03-26 23:05 ` Yonghong Song
2021-03-26 23:12 ` Alexei Starovoitov
2021-03-26 23:17 ` Yonghong Song
2021-03-29 14:04 ` Arnaldo Carvalho de Melo
2021-03-26 15:18 ` Arnaldo Carvalho de Melo
2021-03-26 23:21 ` Andrii Nakryiko [this message]
2021-03-27 0:19 ` Yonghong Song
2021-03-25 13:10 ` [PATCH dwarves 0/3] add option to merge more dwarf cu's into Arnaldo Carvalho de Melo
2021-03-26 1:41 ` Yonghong Song
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='CAEf4BzZ=jWb7KuR6yX+3A4zZUbrgHm=AdxcYVoQ358N5zLGFqw@mail.gmail.com' \
--to=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=arnaldo.melo@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=morbo@google.com \
--cc=yhs@fb.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).