From: "Ondřej Bílka" <neleai@seznam.cz>
To: Will Newton <will.newton@linaro.org>
Cc: 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: Mon, 15 Apr 2013 13:38:00 -0000 [thread overview]
Message-ID: <20130415133829.GA14170@domone.kolej.mff.cuni.cz> (raw)
In-Reply-To: <CANu=Dmig+mxXWNc_c7tJZr4wuhYdQvFdADrLp0eDhapeCNvuvw@mail.gmail.com>
On Mon, Apr 15, 2013 at 11:59:27AM +0100, Will Newton wrote:
> On 15 April 2013 11:23, OndÅ™ej BÃlka <neleai@seznam.cz> wrote:
> > On Mon, Apr 15, 2013 at 11:01:37AM +0100, Will Newton wrote:
> >> Attached are a set of benchmarks of the new code versus the existing
> >> memcpy implementation on a Cortex-A15 platform.
> >>
> >
> > As I wrote at previous thread:
> >
> > On Thu, Apr 04, 2013 at 08:37:01AM +0200, OndÅ™ej BÃlka wrote:
> >> Try also benchmark with real world data (20MB). I put it on
> >> http://kam.mff.cuni.cz/~ondra/dryrun_memcpy.tar.bz2
> >>
> >> To add neon copy test_generic.c file and add compiling neon
> >> implementation to benchmark script.
> >>
> >> It now only measures total time.
> >> I would need something like timestamp counter for more detailed
> >> results.
> >
> > How good it fares on my benchmark?
>
> It wasn't clear to me how to integrate my code and run the tests - I
> built a version of replay.c with each memcpy implementation and the
> new one ran in 20% less time, but I don't know if I did that
> correctly.
>
Nice, this looks correct as that big improvement cannot happen by
chance.
Do you plan improve memset in same way? First step would be take memcpy
and replace loads with zero register.
Ondra
next prev parent reply other threads:[~2013-04-15 13:38 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 [this message]
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
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=20130415133829.GA14170@domone.kolej.mff.cuni.cz \
--to=neleai@seznam.cz \
--cc=libc-ports@sourceware.org \
--cc=patches@linaro.org \
--cc=will.newton@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).