On Fri, May 10, 2024 at 02:15:09PM +0900, Sergey Senozhatsky wrote: > > Well, I asked crypto folks if that's doable and the only reply was > "did you try using compression libs directly". And that's not a > bad response, I take it. Sorry, I've been busy but I was going to get back to you on this. > But in general case, a typical crypto API usage > > tfm = crypto_alloc_comp(comp->name, 0, 0); > > should become much more complex. I'd say that, probably, developing > an entirely new sub-set of API would be simpler. We could easily add a setparams interface for acomp to support this. The form of parameters would be specific to each individual algorithm (but obviously all drivers for the same algorithm must use the same format). Let me hack something up for you. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
