From: Mayshao-oc <Mayshao-oc@zhaoxin.com>
To: Noah Goldstein <goldstein.w.n@gmail.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
GNU C Library <libc-alpha@sourceware.org>,
Florian Weimer <fw@deneb.enyo.de>,
"Carlos O'Donell" <carlos@redhat.com>,
"Louis Qi(BJ-RD)" <LouisQi@zhaoxin.com>
Subject: Re: Re: [PATCH v1 3/6] x86: Remove mem{move|cpy}-ssse3
Date: Thu, 31 Mar 2022 04:54:55 +0000 [thread overview]
Message-ID: <991a21f7e3784cf99c1e725347acbea4@zhaoxin.com> (raw)
In-Reply-To: <CAFUsyf+d9tRY0-WYSDw-OQDGZVpQL_tgbsDwZi3BL8cpHdm+iQ@mail.gmail.com>
On Thur, Mar 31, 2022 at 11:47 AM Noah Goldstein<goldstein.w.n@gmail.com> wrote:
> On Wed, Mar 30, 2022 at 10:34 PM Mayshao-oc <Mayshao-oc@zhaoxin.com> wrote:
> >
> > On Thur, Mar 31, 2022 at 12:45 AM Noah Goldstein<goldstein.w.n@gmail.com> wrote:
> >
> >
> > > On Wed, Mar 30, 2022 at 4:57 AM Mayshao-oc <Mayshao-oc@zhaoxin.com> wrote:
> > > >
> > > > On Tue, Mar 29, 2022 at 10:57 AM Noah Goldstein<goldstein.w.n@gmail.com> wrote:
> > > >
> > > >
> > > > >On Mon, Mar 28, 2022 at 9:51 PM Mayshao-oc <Mayshao-oc@zhaoxin.com> wrote:
> > > > > >
> > > > > > On Mon, Mar 28, 2022 at 9:07 PM H.J. Lu <hjl.tools@gmail.com> wrote:
> > > > > >
> > > > > >
> > > > > > > On Mon, Mar 28, 2022 at 1:10 AM Mayshao-oc <Mayshao-oc@zhaoxin.com> wrote:
> > > > > > > >
> > > > > > > > On Fri, Mar 25, 2022 at 6:36 PM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
> > > > > > > >
> > > > > > > > > With SSE2, SSE4.1, AVX2, and EVEX versions very few targets prefer
> > > > > > > > > SSSE3. As a result its no longer with the code size cost.
> > > > > > > > > ---
> > > > > > > > > sysdeps/x86_64/multiarch/Makefile | 2 -
> > > > > > > > > sysdeps/x86_64/multiarch/ifunc-impl-list.c | 15 -
> > > > > > > > > sysdeps/x86_64/multiarch/ifunc-memmove.h | 18 +-
> > > > > > > > > sysdeps/x86_64/multiarch/memcpy-ssse3.S | 3151 --------------------
> > > > > > > > > sysdeps/x86_64/multiarch/memmove-ssse3.S | 4 -
> > > > > > > > > 5 files changed, 7 insertions(+), 3183 deletions(-)
> > > > > > > > > delete mode 100644 sysdeps/x86_64/multiarch/memcpy-ssse3.S
> > > > > > > > > delete mode 100644 sysdeps/x86_64/multiarch/memmove-ssse3.S
> > > > > > > >
> > > > > > > > On some platforms, such as Zhaoxin, the memcpy performance of SSSE3
> > > > > > > > is better than that of AVX2, and the current computer system has sufficient
> > > > > > > > disk capacity and memory capacity.
> > > > > > >
> > > > > > > How does the SSSE3 version compare against the SSE2 version?
> > > > > >
> > > > > > On some Zhaoxin processors, the overall performance of SSSE3 is about
> > > > > > 10% higher than that of SSE2.
> > > > > >
> > > > > >
> > > > > > Best Regards,
> > > > > > May Shao
> > > > >
> > > > > Any chance you can post the result from running `bench-memset` or some
> > > > > equivalent benchmark? Curious where the regressions are. Ideally we would
> > > > > fix the SSE2 version so its optimal.
> > > >
> > > > Bench-memcpy on Zhaoxin KX-6000 processor shows that, when length <=4 or
> > > > length >= 128, memcpy SSSE3 can achieve an average performance improvement
> > > > of 25% compared to SSSE2.
> > >
> > > Thanks
> > >
> > > The size <= 4 regression is expected as profiles of SPEC show the [5, 32] sized
> > > copies to significantly hotter.
> > >
> > > Regarding the large sizes, it seems to be because the SSSE3 version avoids
> > > unaligned loads/stores much more aggressively.
> >
> > Agree.
> >
> > > For now we will keep the function. Will look into a replacement that isn't so
> > > costly to code size.
> >
> > Thanks very much for your support.
>
> Will SSE4.1 be an issue for you? I think the only reasonable way to fix this is
> with `pshufb`.
Zhaoxin supports SSE4.1, I think there should be no problem. If you have a
ready patch, I‘d love to try it soon.
Thanks again.
> >
> > > Out of curiosity, is bench-memcpy-random performance also improved with
> > > SSSE3? The jump table / branches generally look really nice in micro-benchmarks
> > > but that may not be fully indicative of how it will performance in an
> > > application.
> >
> > Bench-memcpy-random shows about a 5% performance drop for SSSE3:
>
> Thanks.
>
> > __memcpy_sse2_unaligned __memcpy_ssse3 Improvement(ssse3 over sse2)
> > length=32768 805982 874585 -8.51%
> > length=65536 885317 940458 -6.23%
> > length=131072 929177 979173 -5.38%
> > length=262144 980083 1033130 -5.41%
> > length=524288 1042590 1095560 -5.08%
> > length=1048576 1078020 1127990 -4.64%
> >
> >
> > > >
> > > > I have attached the test results, hope this is what you want to see.
> > > >
> > > > > > > > It is strongly recommended to keep the SSSE3 version.
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > H.J.
prev parent reply other threads:[~2022-03-31 4:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 8:10 Mayshao-oc
2022-03-28 13:07 ` H.J. Lu
2022-03-29 2:51 ` Mayshao-oc
2022-03-29 2:57 ` Noah Goldstein
2022-03-30 9:56 ` Mayshao-oc
2022-03-30 16:45 ` Noah Goldstein
2022-03-30 16:54 ` Noah Goldstein
2022-03-31 3:34 ` Mayshao-oc
2022-03-31 3:47 ` Noah Goldstein
2022-03-31 4:54 ` Mayshao-oc [this message]
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=991a21f7e3784cf99c1e725347acbea4@zhaoxin.com \
--to=mayshao-oc@zhaoxin.com \
--cc=LouisQi@zhaoxin.com \
--cc=carlos@redhat.com \
--cc=fw@deneb.enyo.de \
--cc=goldstein.w.n@gmail.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@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).