linux-kernel - [Question] Do we need remote charging for cpu and cpuacct subsys?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Fri, 02 Jul 2021 08:26:27 -0000
From:   Hao Lee <haolee.swjtu@...il.com>
To:     linux-mm@...ck.org, cgroups@...r.kernel.org,
        linux-kernel@...r.kernel.org
Cc:     tj@...nel.org
Subject: [Question] Do we need remote charging for cpu and cpuacct subsys?

Hi,

memcg currently has a remote charging mechanism that can charge usage to other
memcg instead of the one the task belongs to.

In our environment, we need to account the cpu usage consumed by some kworkers
to a specific cgroup. Thus, we want to introduce a remote-charging mechanism to
cpu and cpuacct subsys in our kernel.

I want to know if the community has a plan to do this?
What will the community approach look like?

I think we need to move the active_memcg to a separated active_cgroup struct,
and the latter will contain active_memcg, active_tg, and active_cpuacct.

Regards,
Hao Lee