This is the mail archive of the
mailing list for the glibc project.
Re: A per-user or per-application ld.so.cache?
- From: Siddhesh Poyarekar <sid at reserved-bit dot com>
- To: Carlos O'Donell <carlos at redhat dot com>
- Cc: GNU C Library <libc-alpha at sourceware dot org>
- Date: Tue, 9 Feb 2016 09:49:32 +0530
- Subject: Re: A per-user or per-application ld.so.cache?
- Authentication-results: sourceware.org; auth=none
- References: <56B8E105 dot 8030906 at redhat dot com> <20160208191155 dot GB1904 at devel dot intra dot reserved-bit dot com> <56B8F710 dot 8050108 at redhat dot com> <20160209032921 dot GC1904 at devel dot intra dot reserved-bit dot com> <56B95E75 dot 40000 at redhat dot com>
On Mon, Feb 08, 2016 at 10:35:17PM -0500, Carlos O'Donell wrote:
> Not similar enough from a performance perspective.
> If you have 15 paths in LD_LIBRARY_PATH, they each need to be searched
> in order to find the DSOs required in the last path entry. If you had
> a per-user cache it's a single cache lookup and an mmap. There is no
> traversal required of any filesystem if you get a hit in the cache.
> Isn't that much better?
> All of the cache machinery is there, we just don't have a per-user
Agreed, it will be better.