public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/24872] __memmove_avx_unaligned_erms() performs significantly much slower than __memcpy_ssse3() Date: Sun, 30 May 2021 01:40:07 +0000 [thread overview] Message-ID: <bug-24872-131-FHzCO38909@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-24872-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=24872 --- Comment #11 from H.J. Lu <hjl.tools at gmail dot com> --- (In reply to 苟浩 from comment #10) > I also encountered a similar problem when I used the stream tool to test the > memory bandwidth. > > On the same machine, centos7 and centos8 are installed. Centos7 uses What is your CPU? > glibc-2.17 and centos8 uses glibc-2.28. The stream test data shows that the > memory performance of centos8 is much worse than that of centos7. > > From the flame diagram, the only difference between the two calls is that > glibc-2.28 uses __memmove_avx_unaligned_erms(), glibc-2.17 uses __memcpy_ > ssse3()。 > > This machine is x86_64. However, under aarch64 architecture, glibc-2.17 and > glibc-2.28 perform almost the same. > > The stream compile command uses: > > # gcc -O3 -mcmodel=large -fopenmp -DSTREAM_ARRAY_SIZE=2147483648 -DNTIMES=30 > stream.c -o stream What is stream.c? -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-05-30 1:40 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-24872-131@http.sourceware.org/bugzilla/> 2020-05-30 15:30 ` jan at jki dot io 2021-03-24 23:46 ` hjl.tools at gmail dot com 2021-03-25 0:05 ` hjl.tools at gmail dot com 2021-03-25 2:42 ` skpgkp2 at gmail dot com 2021-03-25 3:00 ` skpgkp2 at gmail dot com 2021-03-25 5:53 ` skpgkp2 at gmail dot com 2021-03-25 13:04 ` hjl.tools at gmail dot com 2021-03-25 13:05 ` hjl.tools at gmail dot com 2021-03-25 13:16 ` skpgkp2 at gmail dot com 2021-03-25 16:28 ` skpgkp2 at gmail dot com 2021-03-25 16:59 ` skpgkp2 at gmail dot com 2021-05-29 5:54 ` gouhaojake at 163 dot com 2021-05-30 1:24 ` gouhaojake at 163 dot com 2021-05-30 1:40 ` hjl.tools at gmail dot com [this message] 2021-05-30 1:41 ` hjl.tools at gmail dot com 2021-05-30 5:07 ` gouhaojake at 163 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-24872-131-FHzCO38909@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).