From: Marc Ballarin <Ballarin.Marc@gmx.de>
To: James Morris <jmorris@redhat.com>
Cc: torvalds@osdl.org, davem@redhat.com,
linux-kernel@vger.kernel.org, clemens@endorphin.org
Subject: Re: [PATCH] Re-implemented i586 asm AES
Date: Fri, 6 Aug 2004 14:00:12 +0200 [thread overview]
Message-ID: <20040806140012.2dbd92bd.Ballarin.Marc@gmx.de> (raw)
In-Reply-To: <Xine.LNX.4.44.0408060411340.21666-100000@dhcp83-76.boston.redhat.com>
On Fri, 6 Aug 2004 04:24:08 -0400 (EDT)
James Morris <jmorris@redhat.com> wrote:
> This code is a rework of the original Gladman AES code, and does not
> include any supposed BSD licensed work by Jari Ruusu.
>
Will this code work with CONFIG_REGPARM=y ?
> +
> +// An AES (Rijndael) implementation for the Pentium MMX family using
> the NASM+// assembler <http://www.web-sites.co.uk/nasm/>. This version
> only implements+// the standard AES block length (128 bits, 16 bytes)
> with the same interface+// as that used in my C/C++ implementation.
> This code does not preserve the+// eax, ecx or edx registers or the
> artihmetic status flags. However, the ebx, +// esi, edi, and ebp
> registers are preserved across calls. Only encryption+// and
> decryption are implemented here, the key schedule code being that
> from+// compiling aes.c with USE_ASM defined. This code uses VC++
> register saving+// conentions// if it is used with another compiler, its
> conventions for using+// and saving registers will need to be checked.
> +
This comment seems partly obsolete.
> config CRYPTO_AES
> tristate "AES cipher algorithms"
> - depends on CRYPTO
> + depends on CRYPTO && !(X86 && !X86_64)
> help
Does it work on x86 CPUs without MMX?
Regards
next prev parent reply other threads:[~2004-08-06 11:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 8:24 James Morris
2004-08-06 8:41 ` David S. Miller
2004-08-06 12:00 ` Marc Ballarin [this message]
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=20040806140012.2dbd92bd.Ballarin.Marc@gmx.de \
--to=ballarin.marc@gmx.de \
--cc=clemens@endorphin.org \
--cc=davem@redhat.com \
--cc=jmorris@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
Powered by JetHome