From: Tejun Heo <tj@kernel.org>
To: LeiZhou-97 <lei.zhou@intel.com>
Cc: lizefan.x@bytedance.com, hannes@cmpxchg.org,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroup/misc: Expose misc.current on cgroup v2 root
Date: Wed, 21 Jun 2023 10:43:49 -1000 [thread overview]
Message-ID: <ZJNhBSAn6qhOLRK0@slm.duckdns.org> (raw)
In-Reply-To: <20230613105929.269318-1-lei.zhou@intel.com>
On Tue, Jun 13, 2023 at 06:59:29PM +0800, LeiZhou-97 wrote:
> Hello,
>
> This patch is to expose misc.current on cgroup v2 root for tracking
> how much of the resource has been consumed in total on the system.
>
> Most of the cloud infrastucture use cgroup to fetch the host
> information for scheduling purpose.
>
> Currently, the misc controller can be used by Intel TDX HKIDs and
> AMD SEV ASIDs, which are both used for creating encrypted VMs.
> Intel TDX and AMD SEV are mostly be used by the cloud providers
> for providing confidential VMs.
>
> In actual use of a server, these confidential VMs may be launched
> in different ways. For the cloud solution, there are kubvirt and
> coco (tracked by kubepods.slice); on host, they can be booted
> directly through qemu by end user (tracked by user.slice), etc.
>
> In this complex environment, when wanting to know how many resource
> is used in total it has to iterate through all existing slices to
> get the value of each misc.current and add them up to calculate
> the total number of consumed keys.
>
> So exposing misc.current to root cgroup tends to give much easier
> when calculates how much resource has been used in total, which
> helps to schedule and count resources for the cloud infrastucture.
>
> Signed-off-by: LeiZhou-97 <lei.zhou@intel.com>
Applied to cgroup/for-6.5.
Thanks.
--
tejun
prev parent reply other threads:[~2023-06-21 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 10:59 LeiZhou-97
2023-06-21 20:43 ` Tejun Heo [this message]
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=ZJNhBSAn6qhOLRK0@slm.duckdns.org \
--to=tj@kernel.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=lei.zhou@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®