From: Phil Blundell <pb@pbcl.net>
To: Mark Hatle <mark.hatle@windriver.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: Prelink problems -- need help!
Date: Mon, 26 Oct 2015 16:50:20 +0000 [thread overview]
Message-ID: <1445878220.5251.110.camel@pbcl.net> (raw)
In-Reply-To: <562E58BE.9060003@windriver.com>
On Mon, 2015-10-26 at 11:45 -0500, Mark Hatle wrote:
>
>
> While some of the modern hashing techniques and such do improve run
> -time dynamic
> link performance, there is still a hit that we must take. For
> devices that need
> quick boot times, quick startup, or are memory constrained, the
> prelinker can
> still help. (Memory usage on very small systems is a good example.
> Memory
> usage can be reduced in larger applications by reducing the number of
> Copy-on-write pages required to handle the relocation information.)
Do you have any concrete data on how much of a boot time speedup,
and/or what reduction in dirty pages, you see on a modern image with
prelink versus the same image without?
p.
next prev parent reply other threads:[~2015-10-26 16:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 14:28 Prelink problems -- need help! Mark Hatle
2015-10-26 16:10 ` Phil Blundell
2015-10-26 16:45 ` Mark Hatle
2015-10-26 16:50 ` Phil Blundell [this message]
2015-10-26 16:55 ` Mark Hatle
2015-10-26 21:18 ` Phil Blundell
2015-10-26 21:35 ` Mark Hatle
2015-10-29 18:32 ` Khem Raj
2015-10-29 18:41 ` Mark Hatle
2015-10-27 0:40 ` Mark Hatle
2015-10-30 3:50 ` Prelink status Mark Hatle
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=1445878220.5251.110.camel@pbcl.net \
--to=pb@pbcl.net \
--cc=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.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