From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: Call for testing/opinions: Optimized memset/memcpy
Date: Mon, 15 Jul 2013 14:15:20 +0100 [thread overview]
Message-ID: <20130715131520.GA16220@arm.com> (raw)
In-Reply-To: <loom.20130713T225129-903@post.gmane.org>
On Sat, Jul 13, 2013 at 10:13:12PM +0100, Harm Hanemaaijer wrote:
> Dr. David Alan Gilbert <gilbertd <at> treblig.org> writes:
>
> >
> > You might like to compare with some of the routines at:
> > https://launchpad.net/cortex-strings
> > and some of the numbers at:
> > https://wiki.linaro.org/WorkingGroups/ToolChain/Benchmarks/
>
> That's interesting. I had looked at cortex-strings before but didn't
> dig into it, also because its benchmark program seemed to be limited in
> scope. From the Linaro numbers it seems NEON isn't always a win
> especially on newer Cortex platforms, with large variability across
> different platforms/cores.
As it has been stated in this thread, we shouldn't use Neon for memcpy.
There is a significant overhead with saving/restoring Neon registers,
preemptability.
But Cortex Strings is a good starting point and Linaro is going to port
some of these functions to the Linux kernel for ARMv8 (AArch64).
--
Catalin
next prev parent reply other threads:[~2013-07-15 13:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-13 15:51 Call for testing/opinions: Optimized memset/memcpy Harm Hanemaaijer
2013-07-13 16:48 ` Dr. David Alan Gilbert
2013-07-13 21:13 ` Harm Hanemaaijer
2013-07-15 13:15 ` Catalin Marinas [this message]
2013-07-14 11:19 ` Harm Hanemaaijer
2013-07-14 11:32 ` Dr. David Alan Gilbert
2013-07-14 11:37 ` Ard Biesheuvel
2013-07-14 13:13 ` Russell King - ARM Linux
2013-07-14 13:33 ` Harm Hanemaaijer
2013-07-14 14:09 ` Ard Biesheuvel
2013-07-14 14:32 ` Russell King - ARM Linux
2013-07-13 17:24 ` Willy Tarreau
2013-07-13 21:51 ` Harm Hanemaaijer
2013-07-14 6:13 ` Willy Tarreau
2013-07-14 11:00 ` Harm Hanemaaijer
2013-07-14 13:09 ` Russell King - ARM Linux
2013-07-14 13:59 ` Harm Hanemaaijer
2013-07-14 15:21 ` Siarhei Siamashka
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=20130715131520.GA16220@arm.com \
--to=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.