Hi Sergey, It is good to know that you are planning to move zram to the async crypto API. As you correctly observed, the Intel IAA driver is based on crypto acomp, which is Ok because we are currently working on upstreaming “zswap compression batching” [1] as the first kernel user of IAA. Our plan is to integrate IAA batching with zram, for which the embedded crypto acomp dependencies in iaa_crypto are the first challenge to overcome, while preserving the crypto interface for zswap. I would like to get your thoughts on whether the crypto_acomp batching interface in patch 10 [2] of the above series would be acceptable for zram IAA integration. If not, I was planning to create a layer in the iaa_crypto driver that would allow interfacing with zcomp without crypto. I figured it would be good to get some early feedback from you before I work on a potential zcomp interface for iaa_crypto (which is non-trivial), in light of your plans to move zram to use async crypto. [1] https://patchwork.kernel.org/project/linux-mm/list/?series=958654 [2] https://patchwork.kernel.org/project/linux-mm/patch/20250430205305.22844-11-kanchana.p.sridhar@xxxxxxxxx/ I will add you to [1]. Thanks, Kanchana
