From: Shuo Wang <wangshuo47@huawei.com>
To: <adhemerval.zanella@linaro.org>, <zhangxuelei4@huawei.com>,
<libc-alpha@sourceware.org>
Cc: hushiyuan@huawei.com
Subject: [PATCH] aarch64: revert memcpy optimze for kunpeng to avoid performance degradation
Date: Wed, 20 Jan 2021 17:35:28 +0800 [thread overview]
Message-ID: <20210120093528.19752-1-wangshuo47@huawei.com> (raw)
Update test results and the following mail is the latest test results:
https://sourceware.org/pipermail/libc-alpha/2021-January/121824.html
In fact, commit 863d775c48 did not improve performance in memcpy_10k.
next reply other threads:[~2021-01-20 9:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 9:35 Shuo Wang [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-01-22 1:26 [PATCH] aarch64: revert memcpy optimze for kunpeng to avoid performance degradation Shuo Wang
2021-01-21 1:55 Zhangxuelei (Derek)
2021-01-21 16:41 ` Adhemerval Zanella via Libc-alpha
2021-01-21 16:45 ` Szabolcs Nagy via Libc-alpha
2021-01-20 14:49 Wilco Dijkstra via Libc-alpha
2021-01-20 9:34 Shuo Wang
2021-01-20 7:20 Shuo Wang
2021-01-20 13:09 ` Adhemerval Zanella via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210120093528.19752-1-wangshuo47@huawei.com \
--to=wangshuo47@huawei.com \
--cc=adhemerval.zanella@linaro.org \
--cc=hushiyuan@huawei.com \
--cc=libc-alpha@sourceware.org \
--cc=zhangxuelei4@huawei.com \
/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).