From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Cc: nd <nd@arm.com>
Subject: Re: [PATCH] Improve string benchtest timing
Date: Tue, 21 May 2019 19:41:03 +0530 [thread overview]
Message-ID: <3acd7a7f-c06a-6679-d526-e758d9ff30ab@gotplt.org> (raw)
In-Reply-To: <VI1PR0801MB21278032D57BDC58A680299383070@VI1PR0801MB2127.eurprd08.prod.outlook.com>
On 21/05/19 7:28 PM, Wilco Dijkstra wrote:
> Well the test doesn't actually test misaligned copies - both source and
> destination are always mutually aligned, so any memcpy implementation which
> aligns either source or destination will only do aligned copies.
They were not intended to be mutually misaligned, that was not the
intent of the benchmark since the target application it modeled did not
have such inputs.
> In any case I'm not sure what the test is supposed to measure - the scores are
> identical across all memcpy implementations. The time taken for double the
> copy size is exactly twice as much.
Right, you'll probably only see differences in case of mutually
misaligned inputs.
Siddhesh
next prev parent reply other threads:[~2019-05-21 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 15:39 [PATCH] Improve string benchtest timing Wilco Dijkstra
2019-05-16 14:57 ` Wilco Dijkstra
2019-05-20 18:44 ` Adhemerval Zanella
2019-05-21 7:01 ` Siddhesh Poyarekar
2019-05-21 13:58 ` Wilco Dijkstra
2019-05-21 14:11 ` Siddhesh Poyarekar [this message]
2019-05-21 15:11 ` Patrick McGehearty
2019-05-22 11:11 ` Wilco Dijkstra
2019-05-22 11:27 ` Siddhesh Poyarekar
2019-05-22 12:38 ` Anton Youdkevitch
2019-05-22 13:24 ` Siddhesh Poyarekar
2019-05-22 13:59 ` Anton Youdkevitch
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=3acd7a7f-c06a-6679-d526-e758d9ff30ab@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=Wilco.Dijkstra@arm.com \
--cc=adhemerval.zanella@linaro.org \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.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).