On Tue, Feb 09, 2010 at 10:45:31AM +0200, Dmitry Kasatkin wrote: > Hi, > > Ok... > > But normally kernel client code uses sync API as shash. > > And I provide async hw driver via async ahash API. > That is simply will not be used at all. > > Client must be changed to use async ahash API in order to benefit from > HW crypto. > > Right?
Yes we will convert hash users over to ahash where appropriate, starting with authenc which covers IPsec. 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
