From: Carlos O'Donell <carlos@redhat.com>
To: caiyinyu <caiyinyu@loongson.cn>,
adhemerval.zanella@linaro.org, libc-alpha@sourceware.org,
i.swmail@xen0n.name
Cc: joseph_myers@mentor.com, xuchenghua@loongson.cn
Subject: Re: [PATCH 0/2] LoongArch: Add optimized functions.
Date: Mon, 15 Aug 2022 10:02:03 -0400 [thread overview]
Message-ID: <f01114a6-d12a-7f8b-8106-d4ff95064027@redhat.com> (raw)
In-Reply-To: <20220815085718.4110353-1-caiyinyu@loongson.cn>
On 8/15/22 04:57, caiyinyu wrote:
> Tested on LoongArch machine: gcc 13.0.0, Linux kernel 5.19.0 rc2,
> binutils branch master 2eb132bdfb9.
Could you please post microbenchmark results for these changes?
How much faster are they from the generic versions?
It is important to show a baseline and the improvement, that way future developers
looking to improve on your work can refer back to these posted numbers for the
hardware you used.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2022-08-15 14:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 8:57 caiyinyu
2022-08-15 8:57 ` [PATCH 1/2] LoongArch: Add optimized string functions: str{chr, chrnul, cmp, ncmp} caiyinyu
2022-08-15 8:57 ` [PATCH 2/2] LoongArch: Add optimized function: memmove caiyinyu
2022-08-15 14:02 ` Carlos O'Donell [this message]
2022-08-15 20:46 ` [PATCH 0/2] LoongArch: Add optimized functions Joseph Myers
[not found] ` <ccc3c93d-07d0-ea9b-562c-aeaec8914f20@loongson.cn>
2022-09-02 9:05 ` Fwd: " dengjianbo
2022-09-02 12:27 ` Adhemerval Zanella Netto
[not found] ` <403f78f0-55d9-48cf-c62a-4a0462a76987@loongson.cn>
2022-09-19 2:03 ` dengjianbo
2022-09-19 20:16 ` Adhemerval Zanella Netto
2022-09-20 9:54 ` Xi Ruoyao
2022-09-22 18:05 ` Adhemerval Zanella Netto
2022-09-26 13:49 ` Xi Ruoyao
2022-09-28 14:22 ` Richard Henderson
2022-09-28 16:42 ` Xi Ruoyao
2022-09-28 19:18 ` Richard Henderson
2022-10-10 1:39 ` Lulu Cheng
2022-09-29 3:00 ` Lulu Cheng
2022-09-29 11:45 ` Adhemerval Zanella Netto
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=f01114a6-d12a-7f8b-8106-d4ff95064027@redhat.com \
--to=carlos@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=caiyinyu@loongson.cn \
--cc=i.swmail@xen0n.name \
--cc=joseph_myers@mentor.com \
--cc=libc-alpha@sourceware.org \
--cc=xuchenghua@loongson.cn \
/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).