Re: [PATCH 1/2] mm: vmscan: Split proactive reclaim statistics from direct reclaim statistics

["Hao Jia" <jiahao1@lixiang.com>]

[-- Attachment #1: Type: text/plain, Size: 2288 bytes --]

On 2025/3/19 17:15, Michal Koutný wrote:
> On Wed, Mar 19, 2025 at 10:38:01AM +0800, Hao Jia <jiahao.kernel@gmail.com> 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

声明：这封邮件只允许文件接收者阅读，有很高的机密性要求。禁止其他人使用、打开、复制或转发里面的任何内容。如果本邮件错误地发给了你，请联系邮件发出者并删除这个文件。机密及法律的特权并不因为误发邮件而放弃或丧失。任何提出的观点或意见只属于作者的个人见解，并不一定代表本公司。
Disclaimer: This email is intended to be read only by the designated recipient of the document and has high confidentiality requirements. Anyone else is prohibited from using, opening, copying or forwarding any of the contents inside. If this email was sent to you by mistake, please contact the sender of the email and delete this file immediately. Confidentiality and legal privileges are not waived or lost by misdirected emails. Any views or opinions expressed in the email are those of the author and do not necessarily represent those of the Company.


[-- Attachment #2: Type: text/html, Size: 3511 bytes --]