mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gao Xiang <xiang@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Gao Xiang <xiang@kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-erofs@lists.ozlabs.org, LKML <linux-kernel@vger.kernel.org>,
	SJ Park <sj@kernel.org>, Guenter Roeck <groeck7@gmail.com>
Subject: Re: [PATCH] erofs: fix EROFS_FS_ZIP_LZMA_DEFAULT_MAX_STREAMS on some UP platforms
Date: Mon, 17 Aug 2026 15:48:49 +0800	[thread overview]
Message-ID: <aoK84br1-61FLLXB@XiangdeMacBook-Pro.local> (raw)
In-Reply-To: <CAMuHMdWQO2Lkv4O8=nv6WVtsL1FEk-04RAv=VSZGkro7n0th2g@mail.gmail.com>

Hi Geert,

On Mon, Aug 17, 2026 at 09:32:51AM +0200, Geert Uytterhoeven wrote:
> Hi Gao,
> 

..

> 
> Thanks for your patch, which is now commit a64d500b0078e16e ("erofs: fix
> EROFS_FS_ZIP_LZMA_DEFAULT_MAX_STREAMS on some UP platforms") in v7.2.
> 
> > --- a/fs/erofs/Kconfig
> > +++ b/fs/erofs/Kconfig
> > @@ -134,7 +134,8 @@ config EROFS_FS_ZIP_LZMA
> >  config EROFS_FS_ZIP_LZMA_DEFAULT_MAX_STREAMS
> >         int "EROFS LZMA default maximum decompression streams"
> >         depends on EROFS_FS_ZIP_LZMA
> > -       range 1 NR_CPUS
> > +       range 1 NR_CPUS if SMP
> > +       range 1 1 if !SMP
> >         default 16
> 
> I have just discovered another oddity: when you have less than 16
> CPUS (including SMP=n), this default value is invalid, and "make
> savedefconfig" will always write a line like
> 
>     CONFIG_EROFS_FS_ZIP_LZMA_DEFAULT_MAX_STREAMS=1
> 
> to the defconfig file, even if that is the default suggested value.
> 
> Needlessly polluting the defconfig files could be fixed using:
> 
>     -       default 16
>     +       default 16 if SMP && NR_CPUS >= 16
>     +       default NR_CPUS if SMP

I guess `default NR_CPUS if SMP && NR_CPUS < 16` would be better,
I'm not sure since I'm not handy in Kconfig stuffs.

>     +       default 1 if !SMP
> 
> Thoughts?

In principle, that would be better, but may I ask if there is some
severe consequences out of one extra line of
CONFIG_EROFS_FS_ZIP_LZMA_DEFAULT_MAX_STREAMS=1?

Since it has been fixed for many times, I hope if it could be improved
later if no severe impacts, sigh..

Thanks,
Gao Xiang

> 
> >         help
> >           By default EROFS allocates one LZMA decompression stream per CPU.
> 
> Gr{oetje,eeting}s,
> 
>                         Geert
> 
> -- 
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
> 
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
>                                 -- Linus Torvalds
> 

  reply	other threads:[~2026-08-17  7:48 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 11:47 [PATCH v3] erofs: cap LZMA stream pool size Michael Bommarito
2026-07-17  3:43 ` Gao Xiang
2026-07-21  3:44   ` Gao Xiang
2026-07-28  3:46     ` SJ Park
2026-07-28  6:31       ` Gao Xiang
2026-07-28  6:54         ` SJ Park
2026-08-03  8:09           ` Geert Uytterhoeven
2026-08-03  9:12             ` Uwe Kleine-König
2026-08-11 19:27               ` Geert Uytterhoeven
2026-08-11 19:35                 ` Guenter Roeck
2026-08-11 19:37                   ` Michael Bommarito
2026-08-11 23:36                     ` Gao Xiang
2026-08-12  9:30                       ` Geert Uytterhoeven
2026-08-12 10:54                         ` Gao Xiang
2026-08-12 11:28                           ` Geert Uytterhoeven
2026-08-12 13:11                             ` [PATCH] erofs: fix EROFS_FS_ZIP_LZMA_DEFAULT_MAX_STREAMS on some UP platforms Gao Xiang
2026-08-12 13:34                               ` Geert Uytterhoeven
2026-08-12 14:13                                 ` Gao Xiang
2026-08-12 14:21                               ` SJ Park
2026-08-17  7:32                               ` Geert Uytterhoeven
2026-08-17  7:48                                 ` Gao Xiang [this message]
2026-08-17  8:05                                   ` Geert Uytterhoeven
2026-08-17  8:09                                     ` Gao Xiang
2026-08-17  8:43                                       ` Geert Uytterhoeven
2026-08-17  9:04                                         ` Gao Xiang
2026-08-17  9:21                                           ` Geert Uytterhoeven
2026-08-17  9:47                                             ` Gao Xiang
2026-08-17 10:06                                               ` Gao Xiang
2026-08-12 14:25                           ` [PATCH v3] erofs: cap LZMA stream pool size Guenter Roeck
2026-08-14 18:26                             ` Gao Xiang
2026-08-14 18:44                               ` Guenter Roeck
2026-08-14 18:50                                 ` Gao Xiang
2026-08-14 19:05                                   ` Guenter Roeck
2026-08-15 11:41                                 ` Geert Uytterhoeven
2026-08-15 13:31                                   ` Guenter Roeck

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=aoK84br1-61FLLXB@XiangdeMacBook-Pro.local \
    --to=xiang@kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=groeck7@gmail.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sj@kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®