From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [RFC PATCH] Optimized memcpy routine
Date: Mon, 21 Mar 2016 23:29:26 +0900 [thread overview]
Message-ID: <1458570567-11596-1-git-send-email-shorne@gmail.com> (raw)
Hello,
This patch is to show what I have been doing and what methods I have tried to
provide an optimized memcpy routing. As you can see from the results above the
numbers are promosing and working well. If no big opposition for a few days I
will update the patch to remove the Kconfig stuff only use the
`word copies + loop unrolls` implementation.
Thanks
-Stafford
Stafford Horne (1):
openrisc: Add optimized memcpy routine
arch/openrisc/Kconfig | 61 ++++++
arch/openrisc/TODO.openrisc | 1 -
arch/openrisc/include/asm/string.h | 5 +
arch/openrisc/lib/Makefile | 3 +-
arch/openrisc/lib/memcpy.c | 377 +++++++++++++++++++++++++++++++++++++
5 files changed, 445 insertions(+), 2 deletions(-)
create mode 100644 arch/openrisc/lib/memcpy.c
--
2.5.0
next reply other threads:[~2016-03-21 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 14:29 Stafford Horne [this message]
2016-03-21 14:29 ` [OpenRISC] [PATCH] openrisc: Add optimized memcpy routine Stafford Horne
2016-03-23 4:54 ` Jonas Bonn
2016-03-24 22:06 ` Stafford Horne
2016-03-25 12:18 ` Jeremy Bennett
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=1458570567-11596-1-git-send-email-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=openrisc@lists.librecores.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.