From: Adrian Bunk <bunk@stusta.de>
To: Andreas Steinmetz <ast@domdv.de>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>,
jmorris@redhat.com, davem@davemloft.net, ak@suse.de,
linux-crypto@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [RFC][PATCH 4/4] AES assembler implementation for x86_64
Date: Sun, 17 Apr 2005 21:54:07 +0200 [thread overview]
Message-ID: <20050417195406.GC3625@stusta.de> (raw)
In-Reply-To: <4262B6F5.4060907@domdv.de>
On Sun, Apr 17, 2005 at 09:20:21PM +0200, Andreas Steinmetz wrote:
> The attached patch contains the required changes for the crypto Kconfig
> to enable the usage of the x86_64 AES assembler implementation.
That is not specifically against this patch, but before we add another
AES implementation, I'd like to find a better solution for the general
AES selection.
My original thoughts on this issue are in [1], but this didn't attack
the problem of CRYPTO_DEV_PADLOCK_AES where it might not be known at
compile time whether the hardware will be present.
> Andreas Steinmetz
> diff -rNu linux-2.6.11.2.orig/crypto/Kconfig linux-2.6.11.2/crypto/Kconfig
> --- linux-2.6.11.2.orig/crypto/Kconfig 2005-03-09 09:12:53.000000000 +0100
> +++ linux-2.6.11.2/crypto/Kconfig 2005-04-17 13:10:51.000000000 +0200
>...
> config CRYPTO_AES_586
> tristate "AES cipher algorithms (i586)"
> - depends on CRYPTO && (X86 && !X86_64)
> + depends on CRYPTO && X86 && !X86_64
>...
This doesn't make any difference.
I think the former version was better readable, but that's no strong
opinion.
cu
Adrian
[1] http://www.ussg.iu.edu/hypermail/linux/kernel/0502.3/0518.html
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2005-04-17 19:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 19:20 [RFC][PATCH 4/4] AES assembler implementation for x86_64 Andreas Steinmetz
2005-04-17 19:54 ` Adrian Bunk [this message]
2005-04-17 20:24 ` Andreas Steinmetz
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=20050417195406.GC3625@stusta.de \
--to=bunk@stusta.de \
--cc=ak@suse.de \
--cc=ast@domdv.de \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jmorris@redhat.com \
--cc=linux-crypto@vger.kernel.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