On 2025/3/19 17:15, Michal Koutný wrote:
> On Wed, Mar 19, 2025 at 10:38:01AM +0800, Hao Jia wrote:
>> However, binding the statistics to the memory.reclaim writers may not be
>> suitable for our scenario. The userspace proactive memory reclaimer triggers
>> proactive memory reclaim on different memory cgroups, and all memory reclaim
>> statistics would be tied to this userspace proactive memory reclaim process.
>
> It thought that was what you wanted -- have stats related precisely to
> the process so that you can feedback-control the reclaim.


What I want is the proactive memory reclamation statistics for each
memory cgroup.

>
>> This does not distinguish the proactive memory reclaim status of different
>> cgroups.
>
> a
> `- b
> `- c
>
> Or do you mean that you write to a/memory.reclaim and want to observe
> respective results in {b,c}/memory.stat?

root
`- a `- b`- c

We have a userspace proactive memory reclaim process that writes to
a/memory.reclaim, observes a/memory.stat, then writes to
b/memory.reclaim and observes b/memory.stat. This pattern is the same
for other cgroups as well, so all memory cgroups(a, b, c) have the
**same writer**. So, I need per-cgroup proactive memory reclaim statistics.


Thanks,
Hao