Hi Sergey, On Wed, Nov 20, 2024 at 12:15:29PM +0900, Sergey Senozhatsky wrote: > On (24/11/19 15:27), Alexey Romanov wrote: > > Since we use custom backend implementation, we remove the ability > > for users to use algorithms from crypto backend. This breaks > > backward compatibility, user doesn't necessarily use one of the > > algorithms from "custom" backends defined in zram folder. > > Sorry, no, we are not adding this for a hypothetical scenario. > > > For example, he can use some driver with hardware compression support. > > Such as? Pretty much all H/W compression modules (I'm aware of) > that people use with zram are out-of-tree. At least we have this: drivers/crypto/nx/nx-common-powernv.c:1043: .cra_flags = CRYPTO_ALG_TYPE_COMPRESS, drivers/crypto/nx/nx-common-pseries.c:1020: .cra_flags = CRYPTO_ALG_TYPE_COMPRESS, drivers/crypto/cavium/zip/zip_main.c:377: .cra_flags = CRYPTO_ALG_TYPE_COMPRESS, drivers/crypto/cavium/zip/zip_main.c:392: .cra_flags = CRYPTO_ALG_TYPE_COMPRESS, Anyway, if we want to completely abandon Crypto API, these modules still need to be supported in zram. -- Thank you, Alexey
