From: Rich Felker <dalias@libc.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Mikael Pettersson <mikpelinux@gmail.com>,
Russ Cox <rsc@golang.org>, Linux API <linux-api@vger.kernel.org>,
Ian Taylor <iant@golang.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
X86 ML <x86@kernel.org>
Subject: Re: [RFC 0/2] __vdso_findsym
Date: Mon, 16 Jun 2014 02:39:08 -0400 [thread overview]
Message-ID: <20140616063907.GX179@brightrain.aerifal.cx> (raw)
In-Reply-To: <CALCETrXxG3_wxRAPF9CNk+2yv7t2Hw5Z4R-UdNKSZtU+pSe9og@mail.gmail.com>
On Sun, Jun 15, 2014 at 11:22:48AM -0700, Andy Lutomirski wrote:
> >>[1] The only comprehensible description of the GNU hash extension that
> >>I could find is on Oracle's blog (!)
> >>
> >
> > Curious about this blog. We do have a GNU hash implementation in Syslinux, too, for another reference.
> >
>
> https://blogs.oracle.com/ali/entry/gnu_hash_elf_sections
>
> FWIW, I bet that __vdso_findsym could be smaller if it used the GNU
> hash. Maybe it would save about the same amount of space that turning
> on the GNU hash would take up.
How so? My implementation of gnu hash lookup in musl's dynamic linker
is somewhat larger than the sysv hash lookup, and that's even with
skipping the bloom filter (which did not seem to yield any benefit,
though we may revisit this issue later). The actual hash function is
_slightly_ smaller for gnu, but the lookup function has a lot more
work to do.
Of course for the size of vdso's symbol table, a pure linear search
with no hash table would suffice...
Rich
next prev parent reply other threads:[~2014-06-16 6:40 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-14 18:16 Andy Lutomirski
2014-06-14 18:16 ` [RFC 1/2] uapi: Add some missing dynamic table-related definitions to elf.h Andy Lutomirski
2014-06-14 18:16 ` [RFC 2/2] [NOT READY] x86/vdso: Add __vdso_findsym Andy Lutomirski
2014-06-14 21:30 ` [RFC 0/2] __vdso_findsym Rich Felker
2014-06-14 22:38 ` Andy Lutomirski
2014-06-14 23:36 ` H. Peter Anvin
2014-06-15 3:59 ` H. Peter Anvin
2014-06-15 6:49 ` Andy Lutomirski
2014-06-15 14:25 ` Mikael Pettersson
2014-06-15 14:35 ` Rich Felker
2014-06-15 15:47 ` Andy Lutomirski
2014-06-15 17:05 ` H. Peter Anvin
2014-06-15 17:40 ` Andy Lutomirski
2014-06-15 17:57 ` H. Peter Anvin
2014-06-15 18:20 ` Andy Lutomirski
2014-06-15 18:39 ` H. Peter Anvin
2014-06-15 18:54 ` Andy Lutomirski
2014-06-15 19:14 ` H. Peter Anvin
2014-06-15 19:22 ` Ian Lance Taylor
2014-06-15 19:31 ` H. Peter Anvin
2014-06-15 19:50 ` Ian Lance Taylor
2014-06-15 19:56 ` H. Peter Anvin
2014-06-15 20:53 ` Andy Lutomirski
2014-06-15 21:13 ` H. Peter Anvin
2014-06-16 0:55 ` Rich Felker
2014-06-16 2:36 ` Andi Kleen
2014-06-16 3:49 ` Rich Felker
2014-06-16 14:08 ` Ian Lance Taylor
2014-06-16 14:38 ` Andi Kleen
2014-06-16 14:58 ` Rich Felker
2014-06-16 15:31 ` Ian Lance Taylor
2014-06-16 15:42 ` Rich Felker
2014-06-20 15:55 ` Andy Lutomirski
2014-06-20 16:07 ` Rich Felker
2014-06-16 14:56 ` Rich Felker
2014-06-15 18:20 ` H. Peter Anvin
2014-06-15 18:22 ` Andy Lutomirski
2014-06-16 6:39 ` Rich Felker [this message]
2014-06-16 1:06 ` Rich Felker
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=20140616063907.GX179@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=hpa@zytor.com \
--cc=iant@golang.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mikpelinux@gmail.com \
--cc=rsc@golang.org \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®