On Thu, Aug 20, 2015 at 03:34:57PM +0900, Joonsoo Kim wrote: > Until now, tfm object embeds (de)compression context in it and > (de)compression in crypto API requires tfm object to use > this context. But, there are some algorithms that doesn't need > such context to operate. Therefore, this patch introduce new crypto > compression API that call (de)compression function via crypto_alg, > instead of tfm object. crypto_alg is required to get appropriate > (de)compression function pointer. This can reduce overhead of > maintaining multiple tfm if (de)compression doesn't require > any context to operate. > > Signed-off-by: Joonsoo Kim <iamjoonsoo.kim@xxxxxxx> This isn't going to fly I'm afraid. The main purpose of a tfm is not to allocate memory but to track the crypto_alg object which could be a hardware device. So you're not going to get away with not allocating it. What you can do for these contextless algorithms (and by definition every compression algorithm is conxteless) is to allocate a system- wide tfm that is used by everybody, or at least by every one within your subsystem. Cheers, -- 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-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
