From: Andi Kleen <ak@muc.de>
To: Bob Deblier <bob.deblier@telenet.be>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AES assembler optimizations
Date: Mon, 09 Aug 2004 16:28:13 +0200 [thread overview]
Message-ID: <m3d620v11e.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <2riR3-7U5-3@gated-at.bofh.it> (Bob Deblier's message of "Mon, 09 Aug 2004 16:00:09 +0200")
Bob Deblier <bob.deblier@telenet.be> writes:
> Just picked up on KernelTrap that there were some problems with
> optimized AES code; if you wish, I can provide my own LGPL licensed (or
> I can relicense them for you under GPL), as included in the BeeCrypt
> Cryptography Library.
>
> I have generic i586 code and SSE-optimized code available in GNU
> assembler format. Latest version is always available on SourceForge
> (http://sourceforge.net/cvs/?group_id=8924).
Would be interesting. Do you have any benchmarks for your code?
However I think we would need to get rid of the M4 first. I don't
think it would be a good idea to add that as kernel build dependency.
Linux kernel assembly normally uses the C preprocessor and modern gas
also has a quite powerful macro facility that is usually good
enough. Any chance to convert the code to one of these?
-Andi
next parent reply other threads:[~2004-08-09 14:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2riR3-7U5-3@gated-at.bofh.it>
2004-08-09 14:28 ` Andi Kleen [this message]
2004-08-09 16:02 ` AES assembler optimizations Bob Deblier
2004-08-09 17:12 ` Matti Aarnio
2004-08-10 19:51 ` H. Peter Anvin
2004-08-10 20:36 ` David S. Miller
2004-08-11 1:02 ` Paul Mackerras
2004-08-11 1:25 ` David S. Miller
2004-08-12 20:18 ` Bill Davidsen
2004-08-09 18:16 ` Andi Kleen
2004-08-09 20:20 ` dean gaudet
2004-08-09 13:47 Bob Deblier
2004-08-09 14:32 ` Patrick McFarland
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=m3d620v11e.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=bob.deblier@telenet.be \
--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.