public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cd_songkun at hotmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/19924] TLS performance degradation after dlopen
Date: Thu, 25 Feb 2021 07:31:51 +0000 [thread overview]
Message-ID: <bug-19924-131-XGPcOySubm@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-19924-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=19924
--- Comment #13 from ksong <cd_songkun at hotmail dot com> ---
Refer
https://sourceware.org/pipermail/libc-alpha/2021-February/122626.html
https://patchwork.ozlabs.org/project/glibc/list/?submitter=65667&page=4
Try backport patch form Szabolcs Nagy.
https://patchwork.ozlabs.org/project/glibc/patch/583EBBA0.9060709@arm.com/
https://patchwork.ozlabs.org/project/glibc/patch/583EBB99.8040101@arm.com/
Rebuild glibc.
Exec tls_mini test case.
[ctu-ksong-d1:tls]$LANG=C
/home/ksong/work/package/glibc/build/elf/ld-linux-x86-64.so.2 --library-path
/home/ksong/work/test/tls:/home/ksong/work/package/glibc/build:/home/ksong/work/package/glibc/build/math:/home/ksong/work/package/glibc/build/elf:/home/ksong/work/package/glibc/build/dlfcn:/home/ksong/work/package/glibc/build/nss:/home/ksong/work/package/glibc/build/nis:/home/ksong/work/package/glibc/build/rt:/home/ksong/work/package/glibc/build/resolv:/home/ksong/work/package/glibc/build/crypt:/home/ksong/work/package/glibc/build/mathvec:/home/ksong/work/package/glibc/build/nptl:/lib64
./tls_mini
time: 0.583575
time: 1.244377
time: 0.553654
It has some performance improvements, but not as obvious as the previous
solution.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-02-25 7:31 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-19924-131@http.sourceware.org/bugzilla/>
2021-01-26 10:29 ` fweimer at redhat dot com
2021-01-27 1:44 ` cd_songkun at hotmail dot com
2021-01-27 11:26 ` adhemerval.zanella at linaro dot org
2021-02-02 10:36 ` cd_songkun at hotmail dot com
2021-02-17 19:20 ` rwmacleod at gmail dot com
2021-02-23 2:26 ` cd_songkun at hotmail dot com
2021-02-23 2:47 ` carlos at redhat dot com
2021-02-23 2:48 ` carlos at redhat dot com
2021-02-23 8:10 ` thomas.perret+glibc at gresille dot org
2021-02-25 7:31 ` cd_songkun at hotmail dot com [this message]
2021-02-25 7:33 ` cd_songkun at hotmail dot com
2021-02-25 7:36 ` cd_songkun at hotmail dot com
2021-02-25 9:54 ` cd_songkun at hotmail dot com
2021-03-24 12:08 ` cd_songkun at hotmail dot com
2021-03-24 15:19 ` carlos at redhat dot com
2021-05-18 2:57 ` cd_songkun at hotmail dot com
2021-05-18 10:12 ` cd_songkun at hotmail dot com
2021-05-18 10:13 ` cd_songkun at hotmail dot com
2021-05-18 13:11 ` adhemerval.zanella at linaro dot org
2021-05-19 8:07 ` cd_songkun at hotmail dot com
2021-06-22 11:01 ` cd_songkun at hotmail dot com
2021-12-08 9:38 ` pgowda.cve at gmail dot com
2023-01-05 16:09 ` zimmerma+gcc at loria dot fr
2023-01-06 10:43 ` nsz at gcc dot gnu.org
2023-07-04 13:55 ` gabravier at gmail dot com
2023-09-01 7:22 ` cvs-commit at gcc dot gnu.org
2023-09-01 9:32 ` sam at gentoo dot org
2023-09-01 9:32 ` sam at gentoo dot org
2023-09-04 12:13 ` 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-19924-131-XGPcOySubm@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).