public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Jari Ruusu <jari.ruusu@pp.inet.fi>
Cc: linux-kernel@vger.kernel.org, cryptoapi-devel@kerneli.org
Subject: Re: [PATCH] AES i586-asm optimized
Date: Thu, 11 Sep 2003 11:33:09 -0400	[thread overview]
Message-ID: <3F6095B5.9010100@pobox.com> (raw)
In-Reply-To: <3F5F5A22.956A72A6@pp.inet.fi>

Jari Ruusu wrote:
> Jeff Garzik wrote:
> 
>>On Wed, Sep 10, 2003 at 05:38:59PM +0200, Fruhwirth Clemens wrote:
>>
>>>As tested by hvr[2] this implemention is significantly faster than the C
>>>version.
>>
>>Tested on what processors?  With what kernel config?
>>
>>I would be surprised if a 586-optimized asm was useful on P4.
> 
> 
> It uses classic Pentium instruction set. Speed optimized for my 300 MHz
> Pentium-2 test box. Original Gladman version that I started with was pretty
> fast but I was able to improve performance about 7% over original version.
> 
> On my same 300 MHz P2 test box, assembler implementation is about twice as
> fast as the mainline kernel C implementation.


Neat.  Consider me surprised, then  ;-)

Don't take my message as objection to the merge.  I dunno what DaveM or 
JamesM thinks, but I definitely support merging patches like this.  It 
provides a great example, if nothing else.

Eventually I bet there will be issues about automatic algorithm 
selection:  like the RAID5 code, which benchmarks all available 
algorithms, and selects the fastest one.

	Jeff




  reply	other threads:[~2003-09-11 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10 15:38 [PATCH] AES i586-asm optimized Fruhwirth Clemens
2003-09-10 16:17 ` Jeff Garzik
2003-09-10 17:06   ` Jari Ruusu
2003-09-11 15:33     ` Jeff Garzik [this message]
2003-09-11 22:14       ` bill davidsen

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=3F6095B5.9010100@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=cryptoapi-devel@kerneli.org \
    --cc=jari.ruusu@pp.inet.fi \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox