All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Pfaff <blp@cs.stanford.edu>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re-implemented i586 asm AES (updated)
Date: Fri, 06 Aug 2004 10:17:43 -0700	[thread overview]
Message-ID: <87ekmkw5hk.fsf@benpfaff.org> (raw)
In-Reply-To: Pine.LNX.4.58.0408060941550.24588@ppc970.osdl.org

Linus Torvalds <torvalds@osdl.org> writes:

> On Fri, 6 Aug 2004, Andi Kleen wrote:
>> 
>> You could use .altinstructions to patch a jump in at runtime
>> based on CPU capabilities. Assuming MMX is really faster of course.
>
> I seriously doubt that the MMX code could be faster.

For what it's worth, about a year about I tested both Gladman's
MMX and non-MMX code on a Pentium 4.  The non-MMX code was
consistently significantly faster in every scenario I could come
up with.
-- 
I love deadlines.
I love the whooshing noise they make as they go by.
--Douglas Adams


  reply	other threads:[~2004-08-06 17:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <2qbyt-1Op-45@gated-at.bofh.it>
     [not found] ` <2qemF-3Pj-49@gated-at.bofh.it>
2004-08-06 15:09   ` [PATCH] Re-implemented i586 asm AES (updated) Andi Kleen
2004-08-06 16:17     ` James Morris
2004-08-06 16:38       ` David Woodhouse
2004-08-06 16:44       ` Jörn Engel
2004-08-06 16:43     ` Linus Torvalds
2004-08-06 17:17       ` Ben Pfaff [this message]
2004-08-07  7:49       ` Kasper Sandberg
2004-08-07 20:26         ` Andi Kleen
2004-08-09 19:38       ` dean gaudet
2004-08-06 12:00 [PATCH] Re-implemented i586 asm AES Marc Ballarin
2004-08-06 14:52 ` [PATCH] Re-implemented i586 asm AES (updated) James Morris

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=87ekmkw5hk.fsf@benpfaff.org \
    --to=blp@cs.stanford.edu \
    --cc=linux-kernel@vger.kernel.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.