From: Xueyuan Chen <xueyuan.chen21@gmail.com>
To: Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: Xueyuan Chen <xueyuan.chen21@gmail.com>,
Minchan Kim <minchan@kernel.org>, Nhat Pham <nphamcs@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/3] docs: zsmalloc: describe statistics with CONFIG_DEBUG_FS
Date: Wed, 11 Nov 2026 19:50:51 +0800 [thread overview]
Message-ID: <179439785114.2142163.1777880997906503143.b4-reply@b4> (raw)
In-Reply-To: <avQJ5NG99xSRhAwV@google.com>
On 2026-11-11 15:25 +0900, Sergey Senozhatsky wrote:
> On (26/11/09 20:59), Xueyuan Chen wrote:
> > -通过CONFIG_ZSMALLOC_STAT,我们可以通过 ``/sys/kernel/debug/zsmalloc/<user name>``
> > +通过CONFIG_DEBUG_FS,我们可以通过 ``/sys/kernel/debug/zsmalloc/<user name>``
> > 看到zsmalloc内部信息。下面是一个统计输出的例子。::
>
> Just out of curiosity, what does <user name> mean? The stats are at
> /sys/kernel/debug/zsmalloc/zramN/classes, where N is zram device number.
>
>
I guess "user" refers to a zsmalloc user, like zram.
But yeah, <pool-name> is clearer. I'll fix it in v3.
prev parent reply other threads:[~2026-11-11 11:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 12:59 [PATCH v2 0/3] mm/zsmalloc: remove CONFIG_ZSMALLOC_STAT 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
2026-11-11 11:29 ` Xueyuan Chen
2026-11-11 11:21 ` Xueyuan Chen
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 11:31 ` Xueyuan Chen
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
2026-11-11 11:40 ` Xueyuan Chen
2026-11-11 6:25 ` Sergey Senozhatsky
2026-11-11 11:50 ` Xueyuan Chen [this message]
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=179439785114.2142163.1777880997906503143.b4-reply@b4 \
--to=xueyuan.chen21@gmail.com \
--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=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
all inboxes | Powered by JetHome®