Re: [PATCH 4/6] zram: Add QPaCE zcomp backend
flat view
From: Sergey Senozhatsky <senozhatsky@chromium.org>
Date: 2026-10-01 10:27:40
Also in:
linux-arm-msm, linux-block, linux-devicetree, lkml
On (26/10/01 10:51), Krzysztof Kozlowski wrote:
On Wed, Sep 30, 2026 at 07:52:13AM -0700, Georgi Djakov wrote:quoted
Add a zcomp backend for the Qualcomm Page Compression Engine (QPaCE) so zram can expose qpace-lz4 as a selectable compression algorithm when the QPaCE driver is available. Compress and decompress operations are handled via the QPaCE urgent synchronous path: each request DMA-maps the source and destination buffers, issues a blocking hardware command, and returns the result size. Signed-off-by: Georgi Djakov <redacted> --- drivers/block/zram/Kconfig | 11 +++ drivers/block/zram/Makefile | 1 + drivers/block/zram/backend_qpace.c | 134 +++++++++++++++++++++++++++++So entire qpace should go here, no? Why did you create this entire layer of indirection, singleton management under drivers/soc?
qpace seems to be standalone/independent arch/soc specific, and can gain users outside of zram (fs compression, zswap, etc.). zram's backends potentially can disappear all together, if we switch to acomp crypto API.