From: Jeff Garzik <jgarzik@pobox.com>
To: manfred@colorfullife.com, akpm@osdl.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] optimize ia32 memmove
Date: Tue, 30 Dec 2003 02:32:09 -0500 [thread overview]
Message-ID: <3FF129F9.7080703@pobox.com> (raw)
In-Reply-To: <200312300713.hBU7DGC4024213@hera.kernel.org>
Linux Kernel Mailing List wrote:
> ChangeSet 1.1496.22.32, 2003/12/29 21:45:30-08:00, akpm@osdl.org
>
> [PATCH] optimize ia32 memmove
>
> From: Manfred Spraul <manfred@colorfullife.com>
>
> The memmove implementation of i386 is not optimized: it uses movsb, which is
> far slower than movsd. The optimization is trivial: if dest is less than
> source, then call memcpy(). markw tried it on a 4xXeon with dbt2, it saved
> around 300 million cpu ticks in cache_flusharray():
[...]
> diff -Nru a/include/asm-i386/string.h b/include/asm-i386/string.h
> --- a/include/asm-i386/string.h Mon Dec 29 23:13:20 2003
> +++ b/include/asm-i386/string.h Mon Dec 29 23:13:20 2003
> @@ -299,14 +299,9 @@
> static inline void * memmove(void * dest,const void * src, size_t n)
> {
> int d0, d1, d2;
> -if (dest<src)
> -__asm__ __volatile__(
> - "rep\n\t"
> - "movsb"
> - : "=&c" (d0), "=&S" (d1), "=&D" (d2)
> - :"0" (n),"1" (src),"2" (dest)
> - : "memory");
> -else
> +if (dest<src) {
> + memcpy(dest,src,n);
> +} else
> __asm__ __volatile__(
> "std\n\t"
> "rep\n\t"
Dumb question, though... what about the overlap case, when dest<src ?
It seems to me this change is ignoring that.
Jeff
next parent reply other threads:[~2003-12-30 7:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200312300713.hBU7DGC4024213@hera.kernel.org>
2003-12-30 7:32 ` Jeff Garzik [this message]
2003-12-30 7:51 ` [PATCH] optimize ia32 memmove Andrew Morton
2003-12-30 7:56 ` Jeff Garzik
2003-12-30 8:11 ` Andrew Morton
2003-12-30 8:11 ` Andreas Dilger
2003-12-30 10:05 ` Linus Torvalds
2003-12-30 9:58 ` Linus Torvalds
2003-12-30 10:17 ` Jeremy Fitzhardinge
2003-12-30 11:12 ` Manfred Spraul
2003-12-30 20:17 ` H. Peter Anvin
2003-12-30 10:21 ` Ed Sweetman
2003-12-30 10:37 ` Andrew Morton
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=3FF129F9.7080703@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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.