[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YN+Sne76dhKBzV/R@mtj.duckdns.org>
Date: Fri, 2 Jul 2021 12:26:37 -1000
From: Tejun Heo <tj@...nel.org>
To: Hao Lee <haolee.swjtu@...il.com>
Cc: linux-mm@...ck.org, cgroups@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [Question] Do we need remote charging for cpu and cpuacct subsys?
Hello,
On Fri, Jul 02, 2021 at 08:26:27AM -0000, Hao Lee wrote:
> 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?
Yeah, we need sth like this to account for cpu cycles spent in commont path
but caused by specific cgroups - e.g. memory reclaim, net packet rx and so
on. There were some mentions of needing somthing like that but haven't been
any patchsets or concrete efforts that I know of.
Thanks.
--
tejun
Powered by blists - more mailing lists