public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steve.gargolinski at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/27695] ld.so has poor performance characteristics when loading large quantities of .so files Date: Tue, 08 Feb 2022 22:07:09 +0000 [thread overview] Message-ID: <bug-27695-131-Y73JUqkyKn@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27695-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27695 --- Comment #4 from steve.gargolinski at gmail dot com --- We use a combination of RTLD_LOCAL and RTLD_GLOBAL in our program. For the core libraries that most other libraries and plugins depend on, we use RTLD_GLOBAL to load to avoid cross-library exception and RTTI issues. Also, localizing the core libraries prevent our program from “stacked” dynamic loading (e.g., at some later time dynamically loading another shared object that depends on the same core libraries). For small plugins that are self-contained, our program uses RTLD_LOCAL to load them. As to RTLD_NOW, we use that to avoid runtime symbol resolution issues, which can only be found via exhaustive testing when using RTLD_LAZY. If a targeted discussion about our use case would be helpful to dig into more details, we would definitely be willing to do so. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-02-08 22:07 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-27695-131@http.sourceware.org/bugzilla/> 2021-04-05 20:50 ` [Bug dynamic-link/27695] ld " hjl.tools at gmail dot com 2021-04-05 20:57 ` hjl.tools at gmail dot com 2021-04-22 13:15 ` steve.gargolinski at gmail dot com 2022-01-27 15:54 ` hjl.tools at gmail dot com 2022-01-28 11:07 ` fweimer at redhat dot com 2022-01-28 14:16 ` [Bug dynamic-link/27695] ld.so " fweimer at redhat dot com 2022-02-08 22:07 ` steve.gargolinski at gmail dot com [this message] 2022-03-01 10:48 ` fweimer at redhat dot com 2022-03-03 22:56 ` pieterjan.briers at gmail dot com 2022-03-03 23:04 ` pieterjan.briers at gmail dot com 2022-03-03 23:36 ` fche at redhat dot com
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=bug-27695-131-Y73JUqkyKn@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).