From: Zhan Xusheng <zhanxusheng1024@gmail.com>
To: Gao Xiang <xiang@kernel.org>, Chao Yu <chao@kernel.org>
Cc: Yue Hu <zbestahu@gmail.com>,
Jeffle Xu <jefflexu@linux.alibaba.com>,
Sandeep Dhavale <dhavale@google.com>,
Hongbo Li <hongbohbli@tencent.com>,
Chunhai Guo <guochunhai@vivo.com>, Nick Terrell <terrelln@fb.com>,
David Sterba <dsterba@suse.com>,
linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org,
Zhan Xusheng <zhanxusheng@xiaomi.com>
Subject: [PATCH] erofs: cap Zstandard stream pool size
Date: Tue, 28 Jul 2026 10:18:31 +0800 [thread overview]
Message-ID: <20260728021831.1532541-1-zhanxusheng1024@gmail.com> (raw)
From: Zhan Xusheng <zhanxusheng@xiaomi.com>
fs/erofs/decompressor_zstd.c sizes the module-global Zstandard stream
pool from num_possible_cpus() when the zstd_streams module parameter is
unset, and z_erofs_load_zstd_config() then preallocates one workspace per
stream, grown to the largest dictionary of any mounted image (up to
Z_EROFS_ZSTD_MAX_DICT_SIZE, i.e. Z_EROFS_PCLUSTER_MAX_SIZE). On high-CPU
systems this can pin a large amount of vmalloc-backed decoder state until
the erofs module is unloaded, mirroring the LZMA case fixed in commit
c9b47e6b2311 ("erofs: cap LZMA stream pool size").
Bound the default stream count by a new
CONFIG_EROFS_FS_ZIP_ZSTD_DEFAULT_MAX_STREAMS option, default 16, while
preserving the per-image workspace sizing. An explicit zstd_streams
module parameter is still honoured as-is.
Fixes: 7c35de4df105 ("erofs: Zstandard compression support")
Signed-off-by: Zhan Xusheng <zhanxusheng@xiaomi.com>
---
fs/erofs/Kconfig | 14 ++++++++++++++
fs/erofs/decompressor_zstd.c | 3 ++-
2 files changed, 16 insertions(+), 1 deletion(-)
diff --git a/fs/erofs/Kconfig b/fs/erofs/Kconfig
index 8ca1767dafb6..a27114d3c82f 100644
--- a/fs/erofs/Kconfig
+++ b/fs/erofs/Kconfig
@@ -167,6 +167,20 @@ config EROFS_FS_ZIP_ZSTD
If unsure, say N.
+config EROFS_FS_ZIP_ZSTD_DEFAULT_MAX_STREAMS
+ int "EROFS Zstandard default maximum decompression streams"
+ depends on EROFS_FS_ZIP_ZSTD
+ range 1 NR_CPUS
+ default 16
+ help
+ By default EROFS allocates one Zstandard decompression stream per
+ CPU. Each stream preallocates a workspace sized for the largest
+ dictionary of any mounted image (up to 1 MiB), so on systems with
+ many CPUs this can reserve a lot of memory. This caps the default;
+ the zstd_streams module parameter still overrides it.
+
+ If unsure, keep the default of 16.
+
config EROFS_FS_ZIP_ACCEL
bool "EROFS hardware decompression support"
depends on EROFS_FS_ZIP
diff --git a/fs/erofs/decompressor_zstd.c b/fs/erofs/decompressor_zstd.c
index ab318a2400f9..44f9d89674e3 100644
--- a/fs/erofs/decompressor_zstd.c
+++ b/fs/erofs/decompressor_zstd.c
@@ -53,7 +53,8 @@ static int __init z_erofs_zstd_init(void)
{
/* by default, use # of possible CPUs instead */
if (!z_erofs_zstd_nstrms)
- z_erofs_zstd_nstrms = num_possible_cpus();
+ z_erofs_zstd_nstrms = min_t(unsigned int, num_possible_cpus(),
+ CONFIG_EROFS_FS_ZIP_ZSTD_DEFAULT_MAX_STREAMS);
for (; z_erofs_zstd_avail_strms < z_erofs_zstd_nstrms;
++z_erofs_zstd_avail_strms) {
--
2.43.0
next reply other threads:[~2026-07-28 2:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 2:18 Zhan Xusheng [this message]
2026-07-28 6:40 ` [PATCH] erofs: cap Zstandard stream pool size Gao Xiang
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=20260728021831.1532541-1-zhanxusheng1024@gmail.com \
--to=zhanxusheng1024@gmail.com \
--cc=chao@kernel.org \
--cc=dhavale@google.com \
--cc=dsterba@suse.com \
--cc=guochunhai@vivo.com \
--cc=hongbohbli@tencent.com \
--cc=jefflexu@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=terrelln@fb.com \
--cc=xiang@kernel.org \
--cc=zbestahu@gmail.com \
--cc=zhanxusheng@xiaomi.com \
/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