From: Eduard Zingerman <eddyz87@gmail.com>
To: Dominique Martinet <asmadeus@codewreck.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
dwarves@vger.kernel.org, bpf@vger.kernel.org
Subject: Re: ppc64le vmlinuz is huge when building with BTF
Date: Thu, 15 Jun 2023 18:21:14 +0300 [thread overview]
Message-ID: <e2620d326d60acb4e5fbd31a1bc9391b14395dcc.camel@gmail.com> (raw)
In-Reply-To: <8d6c094ec12c32e4166299f4a89be7fa4d0f9360.camel@gmail.com>
On Thu, 2023-06-15 at 18:15 +0300, Eduard Zingerman wrote:
> On Thu, 2023-06-15 at 12:32 +0900, Dominique Martinet wrote:
> > Hi,
> >
> > coming from alpine: https://gitlab.alpinelinux.org/alpine/aports/-/issues/12563
> >
> > alice noticed the kernel packages got quite bigger, in particular for
> > ppc64le I've confirmed that the vmlinuz file size jump when building
> > with BTF:
> > currently released package with BTF:
> > https://dl-cdn.alpinelinux.org/alpine/edge/main/ppc64le/linux-lts-6.1.33-r0.apk
> > 272M boot/vmlinuz-lts
>
> Hi Dominique,
>
> I've just checked the linked apk and it looks like DWARF sections are
> not stripped and take most of the space, e.g.:
>
> $ llvm-objdump --headers boot/vmlinuz-lts | grep \.debug \
> | gawk '{ sum += strtonum("0x"$3); } END { print sum; }' | numfmt --to iec
> 228M
>
> Compare this to BTF sections size:
>
> $ llvm-objdump --headers boot/vmlinuz-lts | grep BTF \
> | gawk '{ sum += strtonum("0x"$3); } END { print sum; }' | numfmt --to iec
> 3,9M
Heh, Alan answered while I was looking into it, sorry for the spam.
>
> >
> > test build without BTF:
> > https://gitlab.alpinelinux.org/martinetd/aports/-/jobs/1049335
> > 44M boot/vmlinuz-lts
> >
> >
> > Is that a known issue?
> > We'll probably just turn off BTF for the ppc64le build for now, but it
> > might be worth checking.
> >
> >
> > While I have your attention, even the x86_64 package grew much bigger
> > than I thought it would, the installed modules directory go from 90MB to
> > 108MB gzipped); it's a 18% increase (including kernel: 103->122MB) which
> > is more than what I'd expect out of BTF.
> > Most users don't care about BTF so it'd be great if they could be built
> > and installed separately (debug package all over again..) or limiting
> > the growth a bit more if possible.
> > I haven't tried yet but at this point ikheaders is probably worth
> > considering instead..
> > Perhaps we're missing some stripping option or something?
> >
> >
> > Thanks!
>
prev parent reply other threads:[~2023-06-15 15:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 3:32 ppc64le vmlinuz is huge when building with BTF Dominique Martinet
2023-06-15 8:39 ` Jiri Olsa
2023-06-15 11:52 ` Dominique Martinet
2023-06-15 14:31 ` Alan Maguire
2023-06-15 20:34 ` Dominique Martinet
2023-06-15 21:19 ` Andrii Nakryiko
2023-06-16 10:58 ` Naveen N Rao
2023-06-16 12:00 ` Dominique Martinet
2023-06-16 17:12 ` Naveen N Rao
2023-06-15 15:15 ` Eduard Zingerman
2023-06-15 15:21 ` Eduard Zingerman [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=e2620d326d60acb4e5fbd31a1bc9391b14395dcc.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=acme@kernel.org \
--cc=asmadeus@codewreck.org \
--cc=bpf@vger.kernel.org \
--cc=dwarves@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox