On Tue, Jun 04, 2024 at 02:09:15PM +0900, Sergey Senozhatsky wrote: > > Alright, so this means > > 1) zram needs to be converted to acomp interface Oops, somehow I was thinking of zswap rather than zram. > 2) scomp drivers that zram is using needs to become acomp compatible > (for example, I don't think I see acomp support in crypto/zstd.c) I think you're still confusing scomp with the legacy compress interface that zram uses. Any algorithm marked as scomp is using the new acomp interface. So zstd is fully available through acomp. > 3) zram needs to support setparam > 4) zram needs to support tfm sharing, so that setparam can be called > once > 5) crypto comp drivers need to start support setparam > > That's quite a bit of work, I should admit. At least we won't be duplicating the compression algorithms. Cheers, -- Email: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx> Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
