From: Phil Blundell <pb@pbcl.net>
To: Szabolcs Nagy <szabolcs.nagy@arm.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
libc-alpha@sourceware.org, mark.hatle@kernel.crashing.org,
"Robert Berger@yocto.user" <robert.berger.yocto.user@gmail.com>,
Nicolas Dechesne <nicolas.dechesne@linaro.org>
Subject: Re: Yocto prelink status
Date: Fri, 21 Jan 2022 18:09:11 +0100 [thread overview]
Message-ID: <20220121170911.GD1021@pbcl.net> (raw)
In-Reply-To: <20220121162320.GI3294453@arm.com>
On Fri, Jan 21, 2022 at 04:23:20PM +0000, Szabolcs Nagy wrote:
> glibc plans to support the DT_RELR format for more compact representation
> of relative relocs. see bug 27924.
>
> (i believe this is used on android/chromeos for the reason you cited.)
Yes. There are actually three problems with large number of RELATIVE relocs:
1. They take up a lot of space in .rel.dyn or equivalent which causes binary
bloat.
2. All of them need to be processed at startup (you can't do them lazily) and
this adds delay before you get to main()
3. Data pages that have had relocations applied to them are now dirty and
unshareable so they occupy more space in memory.
As I understand DT_RELR it solves the first of these but not the other two.
Phil
next prev parent reply other threads:[~2022-01-21 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-20 22:51 Richard Purdie
2022-01-21 10:58 ` Phil Blundell
2022-01-21 16:23 ` Szabolcs Nagy
2022-01-21 17:09 ` Phil Blundell [this message]
2022-02-03 15:26 ` Richard Purdie
2022-02-03 15:43 ` Mark Hatle
-- strict thread matches above, loose matches on Subject: below --
2022-01-19 19:52 Adhemerval Zanella
2022-01-19 20:28 ` Joseph Myers
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=20220121170911.GD1021@pbcl.net \
--to=pb@pbcl.net \
--cc=libc-alpha@sourceware.org \
--cc=mark.hatle@kernel.crashing.org \
--cc=nicolas.dechesne@linaro.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=robert.berger.yocto.user@gmail.com \
--cc=szabolcs.nagy@arm.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 read-only IMAP folder(s) and NNTP newsgroup(s).