Re: [PATCH] crypto: aes - make assembler implementation defaultfor i386 and x86-64

From: Herbert Xu
Date: Mon Jun 18 2012 - 05:02:09 EST


On Tue, Jun 12, 2012 at 09:25:18PM +0300, Jussi Kivilinna wrote:
>
> Well, how about letting arch specific assembler implementations
> replace aes-generic
> completely.. in this case add "depends on !X86" on
> CRYPTO_AES_GENERIC. Hardware
> modules get autoloaded (cpuid/pci/platform/etc) but generic
> assembler implementation
> might as well be replacement as it cannot autoload depending on
> hardware support (or
> it can, but will be always loaded).

Perhaps we can just force a modprobe of a given algorithm at least
once for each boot (when requested for the first time). I think
that should be easy to implement and should solve your problem
scenario.

What do you think?

Thanks,
--
Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/