All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jeff Weber <jwamsc@domain.hid>
Cc: Xenomai Help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] Fwd: dynamic loader latencies
Date: Mon, 29 Aug 2011 15:49:02 +0200	[thread overview]
Message-ID: <4E5B98CE.3000200@domain.hid> (raw)
In-Reply-To: <CAAvA3H_rtX_Js5TVHHWDyK-J4vouEY4LxO9MsvdU-y8TjPVoNA@mail.gmail.com>

On 08/29/2011 03:26 PM, Jeff Weber wrote:
> Bumping this post again in hopes of eliciting comments ...
> 
> Jeff
> 
> ---------- Forwarded message ----------
> From: Jeff Weber <jwamsc@domain.hid>
> Date: Fri, Aug 26, 2011 at 11:34 AM
> Subject: dynamic loader latencies
> To: Xenomai Help <xenomai@xenomai.org>
> 
> 
> The Linux ELF dynamic linker/loader ld-linux.so uses a "lazy" model by
> default, and defers symbol resolution, shared object resolution to the time
> when the symbol is first referenced.  This sounds like a large latency
> threat to dynamically linked RT applications running in primary mode. Can
> this happen, or is this unlikely?
> 
> If this is a latency risk, the only solutions I know of are:
> 
> 1) Statically link all RT applications
> 
> 2) Invoke all dynamically linked applications with LD_BIND_NOW=1 environment
> to force the dynamic loader to resolve all  symbols  at program startup
> 
> 3) Link dynamic applications with "-z now" GNU ld option to effect same as
> 2) above.
> 
> Comments?

The best way to be sure is to run some benches. I never run such
benches, so, cannot answer.

-- 
					    Gilles.


  reply	other threads:[~2011-08-29 13:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-26 16:34 [Xenomai-help] dynamic loader latencies Jeff Weber
2011-08-29 13:26 ` [Xenomai-help] Fwd: " Jeff Weber
2011-08-29 13:49   ` Gilles Chanteperdrix [this message]
2011-08-29 20:32 ` [Xenomai-help] " Philippe Gerum

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=4E5B98CE.3000200@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jwamsc@domain.hid \
    --cc=xenomai@xenomai.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 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.