From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Cupertino Miranda <cupertino.miranda@oracle.com>,
Szabolcs Nagy <Szabolcs.Nagy@arm.com>
Cc: "libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [PATCH] AArch64: Optimize strlen
Date: Thu, 2 Mar 2023 13:07:52 +0000 [thread overview]
Message-ID: <PAWPR08MB89825C2C609D23BB43076D1883B29@PAWPR08MB8982.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <87lekf9xur.fsf@oracle.com>
Hi Cupertino,
> I am attempting to reproduce the presented performance improvements on a
> Ampere Altra processor.
> Can you please detail some more what was your setup and how did you
> measured it.
I measured it on large strings (eg. 1024 bytes) on Neoverse V1. You can run
benchtests/bench-strlen.c and look at results for larger strings. However Altra
is half as wide as V1, so may not see much (or any) benefit. Also note by default
it uses the multiarch/strlen_asimd.S version, not strlen.S.
> BTW, I am not looking to discredit the work, but rather to be able
> to replicate the results on our end to evaluate backporting your patches.
Yes it has been a while since we backported string improvements, so it's a good
idea. Are you talking about the official GLIBC release branches or a private branch?
Cheers,
Wilco
next prev parent reply other threads:[~2023-03-02 13:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 15:53 Wilco Dijkstra
2023-01-13 12:26 ` Szabolcs Nagy
2023-03-02 11:49 ` Cupertino Miranda
2023-03-02 13:07 ` Wilco Dijkstra [this message]
2023-03-02 14:29 ` Cupertino Miranda
-- strict thread matches above, loose matches on Subject: below --
2015-04-15 12:34 [PATCH][AArch64] " Wilco Dijkstra
2015-02-27 15:06 Wilco Dijkstra
2015-01-16 17:39 Wilco Dijkstra
2015-07-06 14:42 ` Marcus Shawcroft
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=PAWPR08MB89825C2C609D23BB43076D1883B29@PAWPR08MB8982.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=Szabolcs.Nagy@arm.com \
--cc=cupertino.miranda@oracle.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).