From: Xueyuan Chen <xueyuan.chen21@gmail.com>
To: Minchan Kim <minchan@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Jens Axboe <axboe@kernel.dk>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Xueyuan Chen <xueyuan.chen21@gmail.com>
Subject: [PATCH RFC 0/3] zram: avoid copying spanning LZ4 objects before decompression
Date: Sun, 22 Nov 2026 01:09:23 +0800 [thread overview]
Message-ID: <20261122-zram-split-decomp-mm-rfc-v1-0-4e69b08c0fed@gmail.com> (raw)
When a compressed object spans two zsmalloc pages, zram copies it into
a contiguous buffer before decompression. This series lets the LZ4 and
LZ4HC backends decode dictionary-free blocks directly from the two
fragments.
I measured the time to swap in 1 GiB of synthetic data on arm64 with
4 KiB pages. Each page started with pseudorandom data of one of 16
lengths, followed by zeros. On this workload, 32.6% of compressed
reads spanned two pages with LZ4 and 34.4% with LZ4HC.
The table shows median swap-in times over seven pairs. The last two
columns summarize the percentage change within each pair.
Codec Workers Baseline (ms) Patched (ms) Median Range
LZ4 1 1403.81 1344.45 -4.21% -4.64% to -1.61%
LZ4 8 222.57 216.36 -2.73% -4.19% to -1.97%
LZ4HC 1 1403.35 1336.99 -4.74% -5.07% to -2.90%
LZ4HC 8 222.10 215.77 -3.16% -4.39% to -1.27%
These timings include both skipping the copy and switching decoders.
I used Codex to help implement this series.
Do you think the swap-in improvement justifies maintaining a second
LZ4 decoder?
Assisted-by: LLM
Signed-off-by: Xueyuan Chen <xueyuan.chen21@gmail.com>
---
Xueyuan Chen (3):
zram: allow backends to decompress from two input buffers
lib/lz4: add safe decompression from two input buffers
zram: use split-input decompression for LZ4 and LZ4HC
drivers/block/zram/backend_lz4.c | 1 +
drivers/block/zram/backend_lz4.h | 19 +++++
drivers/block/zram/backend_lz4hc.c | 2 +
drivers/block/zram/zcomp.c | 28 +++++++
drivers/block/zram/zcomp.h | 8 ++
include/linux/lz4.h | 18 ++++
lib/lz4/lz4_decompress.c | 163 +++++++++++++++++++++++++++++++++++++
7 files changed, 239 insertions(+)
---
base-commit: b95f8bb86713c860ce8536d22a988b949b884d5f
--
Best regards,
Xueyuan
next reply other threads:[~2026-11-21 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-21 17:09 Xueyuan Chen [this message]
2026-11-21 17:09 ` [PATCH RFC 1/3] zram: allow backends to decompress from two input buffers Xueyuan Chen
2026-11-21 17:09 ` [PATCH RFC 2/3] lib/lz4: add safe decompression " Xueyuan Chen
2026-11-21 17:09 ` [PATCH RFC 3/3] zram: use split-input decompression for LZ4 and LZ4HC Xueyuan Chen
2026-11-21 20:15 ` [PATCH RFC 0/3] zram: avoid copying spanning LZ4 objects before decompression Eric Biggers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261122-zram-split-decomp-mm-rfc-v1-0-4e69b08c0fed@gmail.com \
--to=xueyuan.chen21@gmail.com \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minchan@kernel.org \
--cc=senozhatsky@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox