All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominique Martinet <asmadeus@codewreck.org>
To: Jiri Olsa <olsajiri@gmail.com>
Cc: 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 20:52:09 +0900	[thread overview]
Message-ID: <ZIr7aaVpOaP8HjbZ@codewreck.org> (raw)
In-Reply-To: <ZIrONqGJeATpbg3Y@krava>

Jiri Olsa wrote on Thu, Jun 15, 2023 at 10:39:18AM +0200:
> > coming from alpine: https://gitlab.alpinelinux.org/alpine/aports/-/issues/12563
> 
> it's probably burried somewhere in that discussion, but do you have
> kernel version (or commit) where that increase happened?

Unfortunately not -- we've just tried on the 6.1.33 that's the current
alpine lts kernel, but I cannot say since when this started because
we've just enabled BTF recently.

Alpine also doesn't seem to keep old versions of apk files on its
mirrors so while it probably has been happening since it got enabled I
don't know how to check, and the commit enabling BTF has been done
without a MR so there's no test log that'd allow seeing the package size
either :/

> also link for used config would be great

alpine has two configs which both exhibit the issue (raw file link on
commit before removing BTF):
https://gitlab.alpinelinux.org/alpine/aports/-/raw/749ee7117e1437b7ab3ef2590f7f2e3558fda3ef/main/linux-lts/virt.ppc64le.config
Size difference for linux-virt: 219 MiB -> 47 MiB
https://gitlab.alpinelinux.org/alpine/aports/-/raw/749ee7117e1437b7ab3ef2590f7f2e3558fda3ef/main/linux-lts/lts.ppc64le.config
Size difference for linux-lts: 306 MiB -> 74 MiB


We just disabled BTF for this arch for now, I honestly won't have time
to dig further short term as I'm not that involved in this issue and
day job is busy right now.

Thanks,
-- 
Dominique

  reply	other threads:[~2023-06-15 11:54 UTC|newest]

Thread overview: 14+ 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 [this message]
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 10:58           ` Naveen N Rao
2023-06-16 12:00           ` Dominique Martinet
2023-06-16 12:00             ` Dominique Martinet
2023-06-16 17:12             ` Naveen N Rao
2023-06-16 17:12               ` Naveen N Rao
2023-06-15 15:15 ` Eduard Zingerman
2023-06-15 15:21   ` Eduard Zingerman

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=ZIr7aaVpOaP8HjbZ@codewreck.org \
    --to=asmadeus@codewreck.org \
    --cc=acme@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=dwarves@vger.kernel.org \
    --cc=olsajiri@gmail.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 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.