Linux OpenRISC platform development
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: openrisc@lists.librecores.org
Subject: [OpenRISC] [RFC PATCH 0/1 ] Optimized memcpy routine
Date: Tue, 22 Mar 2016 06:36:56 +0900	[thread overview]
Message-ID: <1458596217-14337-1-git-send-email-shorne@gmail.com> (raw)

(resending as there were some reported issues on the mail server)

Hello,

This patch is to show what I have been doing and what methods I have tried in
providing an optimized memcpy routine.  As you can see from the results in the
commit details the numbers are promising and there are 2 word copy optimization
options which both perform well. If no opposition for a few days I will update
the patch to remove the Kconfig stuff and only use the
`word copies + loop unrolls` implementation.

The final patch will be made as a pull request to Stefan's github repo.

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



             reply	other threads:[~2016-03-21 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-21 21:36 Stafford Horne [this message]
2016-03-21 21:36 ` [OpenRISC] [RFC PATCH 1/1] openrisc: Add optimized memcpy routine Stafford Horne
2016-03-21 22:27   ` 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=1458596217-14337-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox