linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: boojin.kim@samsung.com (Boojin Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: lib: use LDRD/STRD for data copy
Date: Wed, 28 Mar 2012 13:10:55 +0900	[thread overview]
Message-ID: <014e01cd0c98$c5e899d0$51b9cd70$%kim@samsung.com> (raw)
In-Reply-To: <012d01cd0c78$7d2f19a0$778d4ce0$%kim@samsung.com>

Boojin Kim wrote:
> > Cc: linux-arm-kernel at lists.infradead.org; 'Catalin Marinas'; 'Nicolas Pitre';
> > kgene.kim at samsung.com
> > Subject: Re: [PATCH 2/2] ARM: lib: use LDRD/STRD for data copy
> >
> > On Tue, Mar 27, 2012 at 09:27:52AM +0900, Boojin Kim wrote:
> > > This patch uses LDRD/STRD that loads and stores data as DWORD unit.
> > > It brings better performance than LDRM/STRM with cortex-a15.
> >
> > Why should I bother looking at this rubbish?  You've been told before
> > that using ldrd and strd unconditionally is not acceptable.  Stop
> > wasting peoples review time.
> This patch brings better memcpy results on Cortex-a15.
Additionally, Following is ARM's memcpy implementation that mentions LDRD/STRD is better for cortex-a15.
http://sourceware.org/ml/newlib/2011/msg00469.html
I'm tring to optimize memcpy for cortex-a15 because it's seems to be worth.
Thank you..

> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2012-03-28  4:10 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
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 [this message]

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='014e01cd0c98$c5e899d0$51b9cd70$%kim@samsung.com' \
    --to=boojin.kim@samsung.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 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 NNTP newsgroup(s).