From: Sergey Senozhatsky <senozhatsky@chromium.org>
To: Nhat Pham <nphamcs@gmail.com>
Cc: Xueyuan Chen <xueyuan.chen21@gmail.com>,
Minchan Kim <minchan@kernel.org>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/3] mm/zsmalloc: remove CONFIG_ZSMALLOC_STAT
Date: Wed, 11 Nov 2026 13:35:37 +0900 [thread overview]
Message-ID: <avPwLHMalD_kzD-z@google.com> (raw)
In-Reply-To: <CAKEwX=M6dJMccGcDqp2S-66cbegdivnB6MqQRj6tQ2u18UH62g@mail.gmail.com>
On (26/11/10 08:00), Nhat Pham wrote:
> On Mon, Nov 9, 2026 at 5:59 AM Xueyuan Chen <xueyuan.chen21@gmail.com> wrote:
> >
> > CONFIG_ZSMALLOC_STAT only controls the debugfs interface. The class
> > counters are updated regardless of this option.
> >
> > Remove the CONFIG_ZSMALLOC_STAT guards and rely on the debugfs API
> > stubs when CONFIG_DEBUG_FS=n. Skip statistics setup silently when
> > debugfs is unavailable.
> >
> > Suggested-by: Nhat Pham <nphamcs@gmail.com>
> > Signed-off-by: Xueyuan Chen <xueyuan.chen21@gmail.com>
> > ---
> > mm/zsmalloc.c | 33 ++-------------------------------
> > 1 file changed, 2 insertions(+), 31 deletions(-)
>
> FWIW, LGTM:
>
> Reviewed-by: Nhat Pham <nphamcs@gmail.com>
>
> But I come from the perspective of large(r) server machines - I'd wait
> for the feedback of embedded folks too :)
>
> Sergey, how do you feel about this direction? We've run the stats
> collection (even before we select CONFIG_ZSMALLOC_STAT to expose the
> stats to userspace) for eons, and it was never a bottleneck AFAICS in
> our fleet... And the stats files seem trivial, relatively speaking?
Yeah I guess I'm fine with this change.
I think this can be just one patch.
next prev parent reply other threads:[~2026-11-11 4:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 12:59 [PATCH v2 0/3] " Xueyuan Chen
2026-11-09 12:59 ` [PATCH v2 1/3] " Xueyuan Chen
2026-11-10 15:00 ` Nhat Pham
2026-11-11 4:35 ` Sergey Senozhatsky [this message]
2026-11-09 12:59 ` [PATCH v2 2/3] mm: " Xueyuan Chen
2026-11-10 15:03 ` Nhat Pham
2026-11-11 4:38 ` Sergey Senozhatsky
2026-11-11 4:33 ` Sergey Senozhatsky
2026-11-11 4:37 ` Sergey Senozhatsky
2026-11-09 12:59 ` [PATCH v2 3/3] docs: zsmalloc: describe statistics with CONFIG_DEBUG_FS Xueyuan Chen
2026-11-10 15:03 ` Nhat Pham
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=avPwLHMalD_kzD-z@google.com \
--to=senozhatsky@chromium.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=nphamcs@gmail.com \
--cc=xueyuan.chen21@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®