From: Chengming Zhou <zhouchengming@bytedance.com>
To: zhang fangzheng <fangzheng.zhang1003@gmail.com>
Cc: 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>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
tkjos@google.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: Tue, 20 Feb 2024 15:09:46 +0800 [thread overview]
Message-ID: <ad844581-2533-4a9c-8367-e14bf7b494d7@bytedance.com> (raw)
In-Reply-To: <CA+kNDJKCbd8ygfsZYELKHjCa0BNUSvMM40zWCnkPo7Hrg=HBhQ@mail.gmail.com>
On 2024/2/20 14:25, zhang fangzheng wrote:
> On Mon, Feb 19, 2024 at 7:29 PM Chengming Zhou
> <zhouchengming@bytedance.com> wrote:
>>
>> 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#
>>
>
> Thank you very much for providing a new way.
> I have the following three questions about the new tool you provided:
> ---- 1. From the introduction, the tool is described as an alternative
> to the crash utility.
> Will the permission requirements have different effects when
> used, user or userdebug?
> ---- 2. The 'Helpers' chapter introduces the simple use of
> common.memory, but there is no output example.
> It involves the use of slab objects, but it also needs to
> provide a specific slab_cache_name,
> which cannot give an intuitive overall information like
> proc/slabinfo.
You can of course use drgn to iterate over all slabs by using the global
"slab_caches" list. (All kernel space is at your hand.)
> I guess it is difficult to achieve direct output of slab
> type (reclaim or unreclaim). I don’t know, right?
It's easy for drgn to inspect each slab's information.
> ---- 3. Regarding the supported versions, is it supported for both
> arm/arm64? I don't seem to have seen any similar instructions.
> Finally, I would like to express my gratitude again. This tool will be
> very helpful for me in other future work.
Please check https://github.com/osandov/drgn for details.
Thanks.
prev parent reply other threads:[~2024-02-20 7:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 3:19 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
[not found] ` <CA+kNDJ+C2b520afauSWbfNK=S1XiNHR_zF32_K-3Rf7R6m3n5Q@mail.gmail.com>
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 ` [PATCH V2 0/2] Introduce slabinfo version 2.2 Chengming Zhou
2024-02-20 6:25 ` zhang fangzheng
2024-02-20 7:09 ` Chengming Zhou [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=ad844581-2533-4a9c-8367-e14bf7b494d7@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