From: Chengming Zhou <zhouchengming@bytedance.com>
To: Fangzheng Zhang <fangzheng.zhang@unisoc.com>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
tkjos@google.com, Fangzheng Zhang <fangzheng.zhang1003@gmail.com>,
Yuming Han <yuming.han@unisoc.com>,
Chunyan Zhang <zhang.lyra@gmail.com>
Subject: Re: [PATCH V2 0/2] Introduce slabinfo version 2.2
Date: Mon, 19 Feb 2024 19:29:41 +0800 [thread overview]
Message-ID: <5cb54690-b357-4e7b-ac6f-23fc8dfe575a@bytedance.com> (raw)
In-Reply-To: <20240219031911.10372-1-fangzheng.zhang@unisoc.com>
On 2024/2/19 11:19, Fangzheng Zhang wrote:
> Hi all,
>
> This series introduces slabinfo version 2.2 to users.
> In slabinfo V2.2, we added a slabreclaim column to
> record whether each slab pool is of reclaim type.
> This will be more conducive for users to obtain
> the type of each slabdata more intuitively than through
> the interface /sys/kernel/slab/$cache/reclaim_account.
I want to recommend a better tool: drgn[1] for these tasks, instead of changing
the output format of /proc/slabinfo, which may break existing userspace tools.
[1] https://drgn.readthedocs.io/en/latest/index.html#
> And we have added an example of the output result
> executing '> cat proc/slabinfo' in the file
> Documentation/filesystems/proc.rst.
>
> Changes in v2:
> - Modify the slabinfo version number to 2.2.
> - Add an example of slabinfo output and future works.
>
> Changes in v1:
> - Add a slabreclaim column to record type of each slab
> in file proc/slabinfo.
>
> [1] https://lore.kernel.org/linux-mm/20240131094442.28834-1-fangzheng.zhang@unisoc.com/
>
> Fangzheng Zhang (2):
> mm/slab: Add slabreclaim flag to slabinfo
> Documentation: filesystems: introduce proc/slabinfo to users
>
> Documentation/filesystems/proc.rst | 33 ++++++++++++++++++++++++++++++
> mm/slab_common.c | 9 ++++----
> 2 files changed, 38 insertions(+), 4 deletions(-)
>
next prev parent reply other threads:[~2024-02-19 11:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 3:19 [PATCH V2 0/2] Introduce slabinfo version 2.2 Fangzheng Zhang
2024-02-19 3:19 ` [PATCH V2 1/2] mm/slab: Add slabreclaim flag to slabinfo Fangzheng Zhang
2024-02-19 3:19 ` [PATCH V2 2/2] Documentation: filesystems: introduce proc/slabinfo to users Fangzheng Zhang
2024-02-19 4:24 ` Matthew Wilcox
2024-02-19 6:23 ` zhang fangzheng
2024-02-19 8:09 ` Vlastimil Babka
2024-02-20 8:49 ` zhang fangzheng
2024-02-20 9:21 ` Vlastimil Babka
2024-02-20 9:45 ` zhang fangzheng
2024-02-19 11:29 ` Chengming Zhou [this message]
2024-02-20 6:25 ` [PATCH V2 0/2] Introduce slabinfo version 2.2 zhang fangzheng
2024-02-20 7:09 ` Chengming Zhou
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=5cb54690-b357-4e7b-ac6f-23fc8dfe575a@bytedance.com \
--to=zhouchengming@bytedance.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=fangzheng.zhang1003@gmail.com \
--cc=fangzheng.zhang@unisoc.com \
--cc=gregkh@linuxfoundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=tkjos@google.com \
--cc=vbabka@suse.cz \
--cc=yuming.han@unisoc.com \
--cc=zhang.lyra@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