mailing list of musl libc
 help / color / mirror / code / Atom feed
From: aep <aep@exys.org>
To: <musl@lists.openwall.com>
Subject: Re: Dynamic linker refactoring
Date: Sat, 21 Jan 2012 13:19:40 +0100	[thread overview]
Message-ID: <b4f75a9df9e517a22a5187ec3521de99@exys.org> (raw)
In-Reply-To: <20120121010554.GA8306@brightrain.aerifal.cx>

On Fri, 20 Jan 2012 20:05:54 -0500, Rich Felker wrote:
> Hi all,
>
>  I'm leaning towards stripping out the vdso
> (linux-gate) support at the dynamic linker level entirely, and 
> instead
> using Nik's original design for vdso-assisted clock_gettime which can
> work with static linking too.

isn't the vdso there for much more then just clock_gettime? Ie for a 
whole bunch of syscalls that otherwise need to go through the slow 
interrupt path?


  reply	other threads:[~2012-01-21 12:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-21  1:05 Rich Felker
2012-01-21 12:19 ` aep [this message]
2012-01-22  4:30   ` Rich Felker
2012-01-22 12:45     ` aep

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=b4f75a9df9e517a22a5187ec3521de99@exys.org \
    --to=aep@exys.org \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).