All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hao Lee <haolee.swjtu@gmail.com>
To: linux-mm@kvack.org, cgroups@vger.kernel.org,
	linux-kernel@vger.kernel.org
Cc: tj@kernel.org
Subject: [Question] Do we need remote charging for cpu and cpuacct subsys?
Date: Fri, 02 Jul 2021 08:26:27 -0000	[thread overview]
Message-ID: <60decdb6.1c69fb81.6130e.7642@mx.google.com> (raw)

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

WARNING: multiple messages have this Message-ID (diff)
From: Hao Lee <haolee.swjtu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
	cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org
Subject: [Question] Do we need remote charging for cpu and cpuacct subsys?
Date: Fri, 02 Jul 2021 08:26:27 -0000	[thread overview]
Message-ID: <60decdb6.1c69fb81.6130e.7642@mx.google.com> (raw)

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

             reply	other threads:[~2021-07-02  8:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-02  8:26 Hao Lee [this message]
2021-07-02  8:26 ` [Question] Do we need remote charging for cpu and cpuacct subsys? Hao Lee
2021-07-02  8:26 ` Hao Lee
2021-07-02 20:07 ` Daniel Jordan
2021-07-02 20:19   ` Daniel Jordan
2021-07-02 20:19     ` Daniel Jordan
2021-07-03 16:18   ` Hao Lee
2021-07-03 16:18     ` Hao Lee
2021-07-03 16:18     ` Hao Lee
2021-07-09 15:17     ` Daniel Jordan
2021-07-09 15:17       ` Daniel Jordan
2021-07-02 22:26 ` Tejun Heo
2021-07-02 22:26   ` Tejun Heo
2021-07-03 16:20   ` Hao Lee
2021-07-03 16:20     ` Hao Lee

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=60decdb6.1c69fb81.6130e.7642@mx.google.com \
    --to=haolee.swjtu@gmail.com \
    --cc=cgroups@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=tj@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.