From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: lib: use LDRD/STRD for data copy
Date: Mon, 19 Mar 2012 08:55:03 +0000 [thread overview]
Message-ID: <20120319085503.GL15988@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <007201cd059e$4af2cc10$e0d86430$%kim@samsung.com>
On Mon, Mar 19, 2012 at 04:02:48PM +0900, Boojin Kim wrote:
> This patch uses LDRD/STRD that loads and stores data as DWORD unit
> for the copy of 8-words data.
> It brings better performance than LDRM/STRM that was used originally.
And what about CPUs that don't have ldrd/strd ?
next prev parent reply other threads:[~2012-03-19 8:55 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 7:02 [PATCH] ARM: lib: use LDRD/STRD for data copy Boojin Kim
2012-03-19 8:55 ` Russell King - ARM Linux [this message]
2012-03-19 14:36 ` Rob Herring
2012-03-19 15:41 ` Russell King - ARM Linux
2012-03-19 16:34 ` Måns Rullgård
2012-03-19 16:36 ` Rob Herring
2012-03-19 16:53 ` Nicolas Pitre
2012-03-19 17:11 ` Måns Rullgård
2012-03-19 20:11 ` Michael Hope
2012-03-20 0:21 ` Boojin Kim
2012-03-19 14:10 ` Nicolas Pitre
2012-03-20 0:05 ` Boojin Kim
2012-03-27 0:26 ` [PATCH 1/2] ARM: lib: Add optimized memcpy with 64 byte pld size Boojin Kim
2012-03-27 2:35 ` Nicolas Pitre
2012-03-28 0:28 ` Boojin Kim
2012-03-28 5:23 ` Nicolas Pitre
2012-03-29 4:00 ` [PATCH 0/4] memcpy optimized with strd/ldrd Nicolas Pitre
2012-03-29 4:00 ` [PATCH 1/4] ARM: copy_template.S: move some registers around Nicolas Pitre
2012-03-29 4:00 ` [PATCH 2/4] ARM: copy_template.S: rework the unaligned copy loop Nicolas Pitre
2012-03-29 4:00 ` [PATCH 3/4] ARM: copy_template.S: enforce contigous register set with memory accessors Nicolas Pitre
2012-03-29 4:00 ` [PATCH 4/4] ARM: option to select LDRD/STRD optimized memory copy Nicolas Pitre
2012-03-27 0:27 ` [PATCH 2/2] ARM: lib: use LDRD/STRD for data copy Boojin Kim
2012-03-27 7:40 ` Russell King - ARM Linux
2012-03-28 0:19 ` Boojin Kim
2012-03-28 4:10 ` Boojin Kim
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=20120319085503.GL15988@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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.