From: Will Newton <will.newton@linaro.org>
To: "Ondřej Bílka" <neleai@seznam.cz>
Cc: "Måns Rullgård" <mans@mansr.com>,
libc-ports@sourceware.org, "Patch Tracking" <patches@linaro.org>
Subject: Re: [PATCH] ARM: Add Cortex-A15 optimized NEON and VFP memcpy routines, with IFUNC.
Date: Thu, 18 Apr 2013 09:47:00 -0000 [thread overview]
Message-ID: <CANu=DmiVS4y6Cmdw_K8Gpbp=LjkaQ8Pf6eDvjBfsTcKLmcue3g@mail.gmail.com> (raw)
In-Reply-To: <20130418093900.GA3653@domone.kolej.mff.cuni.cz>
On 18 April 2013 10:39, Ondřej Bílka <neleai@seznam.cz> wrote:
> On Mon, Apr 15, 2013 at 11:38:49AM +0100, Will Newton wrote:
>> On 15 April 2013 11:06, Måns Rullgård <mans@mansr.com> wrote:
>>
>> Hi Måns,
>>
>> >> Add a high performance memcpy routine optimized for Cortex-A15 with
>> >> variants for use in the presence of NEON and VFP hardware, selected
>> >> at runtime using indirect function support.
>> >
>> > How does this perform on Cortex-A9?
>>
>> The code is also faster on A9 although the gains are not quite as
>> pronounced. A set of numbers is attached (they linewrap pretty
>> horribly inline).
>>
>>
> I forget to ask where to get benchmark source. Without it there is no
> way to tell if it was done correctly.
> You must randomly vary sizes in range n..2n and also vary alignments.
The benchmark is taken from the cortex-strings package:
https://launchpad.net/cortex-strings
I wrote a wrapper around the benchmark to vary alignment in {1, 2, 4,
8} and a variety of block lengths between 8 and 200.
--
Will Newton
Toolchain Working Group, Linaro
next prev parent reply other threads:[~2013-04-18 9:47 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 9:57 Will Newton
2013-04-15 10:01 ` Will Newton
2013-04-15 10:23 ` Ondřej Bílka
2013-04-15 10:59 ` Will Newton
2013-04-15 13:38 ` Ondřej Bílka
2013-04-15 10:06 ` Måns Rullgård
2013-04-15 10:38 ` Will Newton
2013-04-15 10:46 ` Måns Rullgård
2013-04-15 10:49 ` Will Newton
2013-04-18 9:39 ` Ondřej Bílka
2013-04-18 9:47 ` Will Newton [this message]
2013-04-18 11:56 ` Ondřej Bílka
2013-04-15 17:14 ` Richard Henderson
2013-04-15 17:44 ` Will Newton
2013-04-15 18:22 ` Richard Henderson
2013-04-15 18:31 ` Will Newton
2013-04-15 18:37 ` Richard Henderson
2013-04-15 18:48 ` Will Newton
2013-04-15 19:12 ` Richard Henderson
2013-04-15 19:47 ` Will Newton
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='CANu=DmiVS4y6Cmdw_K8Gpbp=LjkaQ8Pf6eDvjBfsTcKLmcue3g@mail.gmail.com' \
--to=will.newton@linaro.org \
--cc=libc-ports@sourceware.org \
--cc=mans@mansr.com \
--cc=neleai@seznam.cz \
--cc=patches@linaro.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).