From: Gao Xiang <xiang@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
Gao Xiang <xiang@kernel.org>, Chao Yu <chao@kernel.org>,
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>,
Michael Bommarito <michael.bommarito@gmail.com>,
linux-erofs@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] erofs: Fix EROFS_FS_ZIP_LZMA_DEFAULT_MAX_STREAMS default logic
Date: Thu, 20 Aug 2026 21:10:25 +0800 [thread overview]
Message-ID: <aob8wTTSCuq5054v@XiangdeMacBook-Pro.local> (raw)
In-Reply-To: <3d845134-9b75-40bd-b221-2bd35f98d425@roeck-us.net>
On Thu, Aug 20, 2026 at 05:51:08AM -0700, Guenter Roeck wrote:
> On Thu, Aug 20, 2026 at 12:00:23PM +0200, Geert Uytterhoeven wrote:
> > When NR_CPUS is less than 16, or when SMP is disabled, the default value
> > of 16 is invalid.
> >
> > While actual configuration picks up a sensible and valid default
> > (NR_CPUS or 1), "make savedefconfig" will still write a line like
> >
> > CONFIG_EROFS_FS_ZIP_LZMA_DEFAULT_MAX_STREAMS=1
> >
> > to the defconfig file, even if that matches the sensible default.
> >
> > Avoid needlessly enlarging the defconfig files, and reduce churn for
> > updating them, by specifying valid defaults depending on SMP and
> > NR_CPUS.
> >
> > While at it, make the prompt depend on SMP, as there is no point in
> > asking the user about the maximum number of decompression streams if
> > there is only one valid answer.
> >
>
> Absolutely agree.
As I replied to Geert, unless there is a mandatory requirement
documented that "there is no point to make a Kconfig visible if there
is only one valid number".
I tend to avoid making EROFS Kconfig visibility depend on arbitrary
architecture Kconfig options such as SMP or !SMP; SMP here is due to
some arches make NR_CPUS = 0 if !SMP, but it doesn't need to bother
users why a EROFS kconfig visibility has some relationship with an arch
kconfig.
Thanks,
Gao Xiang
next prev parent reply other threads:[~2026-08-20 13:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 10:00 Geert Uytterhoeven
2026-08-20 10:15 ` Geert Uytterhoeven
2026-08-20 12:51 ` Guenter Roeck
2026-08-20 13:10 ` Gao Xiang [this message]
2026-08-20 13:43 ` Guenter Roeck
2026-08-20 14:20 ` Gao Xiang
2026-08-20 12:56 ` Gao Xiang
2026-08-20 14:20 ` Geert Uytterhoeven
2026-08-24 0:43 ` Chao Yu
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=aob8wTTSCuq5054v@XiangdeMacBook-Pro.local \
--to=xiang@kernel.org \
--cc=chao@kernel.org \
--cc=dhavale@google.com \
--cc=geert+renesas@glider.be \
--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=linux@roeck-us.net \
--cc=michael.bommarito@gmail.com \
--cc=zbestahu@gmail.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
all inboxes | Powered by JetHome®