public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ville.heikkinen at nokia dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/27944] poor TLS performance in shared object after calling dlopen with another shared object that also contains TLS section
Date: Thu, 26 Jan 2023 07:07:00 +0000 [thread overview]
Message-ID: <bug-27944-131-fHXZdJlfgv@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27944-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27944
Ville Heikkinen <ville.heikkinen at nokia dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ville.heikkinen at nokia dot com
--- Comment #2 from Ville Heikkinen <ville.heikkinen at nokia dot com> ---
I can confirm that we have hit this kind of issue while having a plugin
interface that uses dlopen() to load dynamic libraries. This causes the TLS
performance to degrade significantly. We've tested Dzmitry's patch and it seems
to fix the issue.
Could some of the maintainers check this bug and perhaps we could get the fix
to the upstream?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-26 7:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 23:46 [Bug dynamic-link/27944] New: " dzmitry.konanka at karambasecurity dot com
2021-06-03 9:20 ` [Bug dynamic-link/27944] " dzmitry.konanka at karambasecurity dot com
2023-01-26 7:07 ` ville.heikkinen at nokia dot com [this message]
2024-06-03 15:06 ` fweimer 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-27944-131-fHXZdJlfgv@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).