[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c8835a1c-2266-0131-7fd6-e6449750353b@openvz.org>
Date: Sat, 21 May 2022 10:28:47 +0300
From: Vasily Averin <vvs@...nvz.org>
To: Roman Gushchin <roman.gushchin@...ux.dev>
Cc: Michal Koutný <mkoutny@...e.com>,
Shakeel Butt <shakeelb@...gle.com>, kernel@...nvz.org,
linux-kernel@...r.kernel.org, Vlastimil Babka <vbabka@...e.cz>,
Michal Hocko <mhocko@...e.com>, cgroups@...r.kernel.org
Subject: Re: [PATCH 3/4] memcg: enable accounting for struct cgroup
On 5/21/22 03:55, Roman Gushchin wrote:
> On Fri, May 20, 2022 at 11:16:32PM +0300, Vasily Averin wrote:
>> common part:
>> 16 ~ 352 5632 5632 KERNFS (*)
>> 1 + 4096 4096 9728 (cgroup_mkdir+0xe4)
>> 1 584 584 10312 (radix_tree_node_alloc.constprop.0+0x89)
>> 1 192 192 10504 (__d_alloc+0x29)
>> 2 72 144 10648 (avc_alloc_node+0x27)
>> 2 64 128 10776 (percpu_ref_init+0x6a)
>> 1 64 64 10840 (memcg_list_lru_alloc+0x21a)
>>
>> 1 + 192 192 192 call_site=psi_cgroup_alloc+0x1e
>> 1 + 96 96 288 call_site=cgroup_rstat_init+0x5f
>> 2 12 24 312 call_site=percpu_ref_init+0x23
>> 1 6 6 318 call_site=__percpu_counter_init+0x22
>
> I'm curios, how do you generate these data?
trace_cmd + awk + /dev/hand
> Just an idea: it could be a nice tool, placed somewhere in tools/cgroup/...
I'm agree, nice idea. I'll try to implement it.
Powered by blists - more mailing lists