mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fruhwirth Clemens <clemens-dated-1085312570.422b@endorphin.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] AES i586 optimized
Date: Thu, 13 May 2004 13:42:50 +0200	[thread overview]
Message-ID: <20040513114250.GB22233@ghanima.endorphin.org> (raw)
In-Reply-To: <20040513040732.75c5999c.akpm@osdl.org>

On Thu, May 13, 2004 at 04:07:32AM -0700, Andrew Morton wrote:
> Fruhwirth Clemens <clemens-dated-1085310070.4b1f@endorphin.org> wrote:

> >  The following patch adds an i586 optimized implementation of AES aka
> >  Rijndael. It's following an integration strategy similiar to recent
> >  s390/z990 integration for DES/SHA1. aes-i586-glue.c, a glue layer for
> >  CryptoAPI, and aes-i586-asm.S, the actual implementation, are added to
> >  arch/i386/crypto, as well as a config section to crypto/Kconfig.
> 
> Some benchmark figures would be useful.  Cache-cold and cache-hot.

I posted this patch for the first time about 3/4 year ago. The first
response has been the same. Please have a look at

My first posting:
http://marc.theaimsgroup.com/?l=linux-kernel&m=106321924724484&w=2
My original claim:
http://www.kerneli.org/pipermail/cryptoapi-devel/2003-August/000607.html
Jari Ruusu's posting:
http://marc.theaimsgroup.com/?l=linux-kernel&m=106321682117697&w=2

I suspect the result to be similar for a P4 for example. I could do some P4
benchmarking.

> >  The code has been in use for half a year by myself and the loop-aes project
> >  for the last - I think - 2 years. I consider the implementation
> >  production-stable. Andrew, please consider applying.
> 
> James Morris <jmorris@redhat.com> is the crypto guy....

Ack. I'll try to get his opinion on this.

Regards, Clemens

  reply	other threads:[~2004-05-13 11:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-13 11:01 Fruhwirth Clemens
2004-05-13 11:07 ` Andrew Morton
2004-05-13 11:42   ` Fruhwirth Clemens [this message]
2004-05-13 14:05     ` Felipe Alfaro Solana
2004-05-13 15:29       ` [PATCH] AES i586 optimized (oops) Felipe Alfaro Solana
2004-05-13 19:27         ` Felipe Alfaro Solana
2004-05-13 12:34   ` [PATCH] AES i586 optimized Fruhwirth Clemens
2004-05-13 11:13 ` Christoph Hellwig
2004-05-13 11:25   ` Fruhwirth Clemens
2004-05-13 12:18     ` Christoph Hellwig
2004-05-13 12:37       ` Dave Jones
2004-05-13 13:24 ` Christophe Saout
2004-05-13 15:09 ` James Morris
2004-05-13 15:23   ` James Morris
2004-05-13 22:23 ` Felipe Alfaro Solana

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=20040513114250.GB22233@ghanima.endorphin.org \
    --to=clemens-dated-1085312570.422b@endorphin.org \
    --cc=akpm@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®