All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Fruhwirth Clemens <clemens-dated-1064072339.1427@endorphin.org>
Cc: linux-kernel@vger.kernel.org, cryptoapi-devel@kerneli.org
Subject: Re: [PATCH] AES i586-asm optimized
Date: Wed, 10 Sep 2003 12:17:38 -0400	[thread overview]
Message-ID: <20030910161738.GA29990@gtf.org> (raw)
In-Reply-To: <20030910153859.GA17919@leto2.endorphin.org>

On Wed, Sep 10, 2003 at 05:38:59PM +0200, Fruhwirth Clemens wrote:
> This patch[1] adds an i586 assembler optimized version of the Rijndael (AES)
> cipher. Please have a look, try, and criticise.
> 
> Before starting the old "do we need assembler" thread again: 
> 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.


> Guys, the linux kernel doesn't even compile with icc (Intel C
> compiler)

Wrong.  As Intel pointed out on linux-kernel less than 24 hours ago,
even.


> These are the raw numbers. Assembler is faster. 

gcc generates assembler, so this is nonsensical ;-)


> And before we start to discuss a sophisticated framework for assembler
> implemention or automatic selection of implementions or preferences by
> application for a particular implemention and so one: This is the first
> assembler implemention and most likely the last for a long time.

Nope, S/390 folks beat ya to it.

And I'm working on something as well.


> So I think
> with this perspective it's not worth delaying this feature, especially
> because after this module disk encryption becomes reasonable.

In your opinion.

	Jeff




  reply	other threads:[~2003-09-10 16:22 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 [this message]
2003-09-10 17:06   ` Jari Ruusu
2003-09-11 15:33     ` Jeff Garzik
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=20030910161738.GA29990@gtf.org \
    --to=jgarzik@pobox.com \
    --cc=clemens-dated-1064072339.1427@endorphin.org \
    --cc=cryptoapi-devel@kerneli.org \
    --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.