On Mon, Mar 16, 2009 at 12:55:26PM +0100, Steffen Klassert wrote: > > @@ -447,7 +448,7 @@ static int esp_init_aead(struct xfrm_state *x) > struct crypto_aead *aead; > int err; > > - aead = crypto_alloc_aead(x->aead->alg_name, 0, 0); > + aead = crypto_alloc_aead_tfm(x->aead->alg_name, 0, 0);
I'd like this to be configurable. After all, there's not much point in doing this if your crypto is done through PCI. The easiest way is to let the user specify pcrypt through the algorithm name. In fact, as long as pcrypt has a higher priority than the default software algorithms, the user simply has to instantiate it in order for it to be the default for all uses of that algorithm. Cheers, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} <herb...@gondor.apana.org.au> 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-crypto" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
