From: "Albrecht Dreß" <albrecht.dress@arcor.de>
To: Chris Friesen <cfriesen@nortel.com>,
Grant Likely <grant.likely@secretlab.ca>
Cc: Linux kernel <linux-kernel@vger.kernel.org>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Dirk Eibach <eibach@gdsys.de>
Subject: Re: Fwd: [PATCH] arch/powerpc: Improve _memcpy
Date: Wed, 04 Nov 2009 19:12:21 +0100 [thread overview]
Message-ID: <1257358349.2489.0@antares> (raw)
In-Reply-To: <4AF084C6.3020602@nortel.com> (from cfriesen@nortel.com on Tue Nov 3 20:30:14 2009)
[-- Attachment #1: Type: text/plain, Size: 1904 bytes --]
See <http://lists.ozlabs.org/pipermail/linuxppc-dev/2009-May/072582.html>.
Any chance to get this one into the tree? Grant?
Cheers, Albrecht.
Am 03.11.09 20:30 schrieb(en) Chris Friesen:
>
> Forwarding to the ppc mailing list.
>
> Chris
>
>
> -------- Original Message --------
> Subject: [PATCH] arch/powerpc: Improve _memcpy
> Date: Tue, 3 Nov 2009 15:20:56 +0100
> From: Dirk Eibach <eibach@gdsys.de>
> To: linux-kernel@vger.kernel.org
> CC: Dirk Eibach <eibach@gdsys.de>
>
> The implementation of _memcpy_fromio and _memcpy_toio seems to be
> suboptimal for size 4.
>
> Signed-off-by: Dirk Eibach <eibach@gdsys.de>
> ---
> arch/powerpc/kernel/io.c | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/kernel/io.c b/arch/powerpc/kernel/io.c
> index 1882bf4..8dc7547 100644
> --- a/arch/powerpc/kernel/io.c
> +++ b/arch/powerpc/kernel/io.c
> @@ -161,7 +161,7 @@ void _memcpy_fromio(void *dest, const volatile void
> __iomem *src,
> dest++;
> n--;
> }
> - while(n > 4) {
> + while(n >= 4) {
> *((u32 *)dest) = *((volatile u32 *)vsrc);
> eieio();
> vsrc += 4;
> @@ -190,7 +190,7 @@ void _memcpy_toio(volatile void __iomem *dest, const
> void *src, unsigned long n)
> vdest++;
> n--;
> }
> - while(n > 4) {
> + while(n >= 4) {
> *((volatile u32 *)vdest) = *((volatile u32 *)src);
> src += 4;
> vdest += 4;
> --
> 1.5.6.5
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@lists.ozlabs.org
> https://lists.ozlabs.org/listinfo/linuxppc-dev
>
>
[-- Attachment #2: Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2009-11-04 18:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 19:30 Fwd: [PATCH] arch/powerpc: Improve _memcpy Chris Friesen
2009-11-04 18:12 ` Albrecht Dreß [this message]
2009-11-09 17:06 ` Grant Likely
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=1257358349.2489.0@antares \
--to=albrecht.dress@arcor.de \
--cc=cfriesen@nortel.com \
--cc=eibach@gdsys.de \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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