From: Arjan van de Ven <arjanv@redhat.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Arjan van de Ven <arjanv@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [BK+PATCH] remove __constant_memcpy
Date: Fri, 18 Apr 2003 09:06:35 +0000 [thread overview]
Message-ID: <20030418090635.A16232@devserv.devel.redhat.com> (raw)
In-Reply-To: <3E9F3D6F.9030501@pobox.com>; from jgarzik@pobox.com on Thu, Apr 17, 2003 at 07:49:03PM -0400
On Thu, Apr 17, 2003 at 07:49:03PM -0400, Jeff Garzik wrote:
> Three tangents:
> 1) where did the 486 string ops go?
those were slower even on 80486, and broken as well
> 2) why no sse2-optimized memcpy? just that noone has done one yet?
I've not moved the userspace prototype to kernelspace
next prev parent reply other threads:[~2003-04-18 8:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 0:57 [BK+PATCH] remove __constant_memcpy Jeff Garzik
2003-04-17 1:04 ` Jeff Garzik
2003-04-17 2:06 ` Linus Torvalds
2003-04-17 8:46 ` Arjan van de Ven
2003-04-17 9:02 ` Roman Zippel
2003-04-17 9:04 ` Arjan van de Ven
2003-04-17 9:11 ` Jakub Jelinek
2003-04-17 16:07 ` Linus Torvalds
2003-04-17 19:07 ` Jeff Garzik
2003-04-17 19:19 ` Jeff Garzik
2003-04-17 19:54 ` Linus Torvalds
2003-04-17 23:49 ` Jeff Garzik
2003-04-17 23:52 ` Jeff Garzik
2003-04-17 23:59 ` Linus Torvalds
2003-04-18 0:29 ` H. Peter Anvin
2003-04-18 9:06 ` Arjan van de Ven [this message]
2003-04-18 14:31 ` Timothy Miller
2003-04-18 15:07 ` Richard B. Johnson
2003-04-17 22:58 ` J.A. Magallon
2003-04-17 23:10 ` Jeff Garzik
2003-04-17 13:17 ` Alan Cox
2003-04-17 13:17 ` Alan Cox
2003-04-17 14:32 ` Jeff Garzik
2003-04-17 14:40 ` Jeff Garzik
2003-04-17 20:01 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2003-04-17 2:22 Nakajima, Jun
2003-04-17 23:50 Chuck Ebbert
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=20030418090635.A16232@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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.