All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michal Koutný" <mkoutny@suse.com>
To: Sun Shaojie <sunshaojie@kylinos.cn>
Cc: cgroups@vger.kernel.org, corbet@lwn.net, cui.tao@linux.dev,
	 hannes@cmpxchg.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,  skhan@linuxfoundation.org,
	tj@kernel.org
Subject: Re: [PATCH v3] cgroup/cpu: document cpu.stat.local and clarify cpu.stat behavior
Date: Mon, 29 Jun 2026 15:49:59 +0200	[thread overview]
Message-ID: <akJ37sqf6nOTW9hW@localhost.localdomain> (raw)
In-Reply-To: <20260629060636.200118-1-sunshaojie@kylinos.cn>

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

On Mon, Jun 29, 2026 at 02:06:36PM +0800, Sun Shaojie <sunshaojie@kylinos.cn> wrote:
> Add documentation for the cpu.stat.local interface file, which reports
> the throttled_usec stat -- the actual throttling time incurred by the
> cgroup's own runqueues, which may include throttling inherited from
> ancestor cgroup bandwidth limits. Unlike cpu.stat's throttled_usec
> which only accounts for throttling caused by the cgroup's own CFS
> bandwidth limit.
> 
> When the controller is not enabled, the stat is not reported.
> 
> Also clarify cpu.stat descriptions: note that the three base CPU usage
> stats (usage_usec, user_usec, system_usec) include descendant cgroups,
> and that the five CFS bandwidth stats are non-hierarchical -- they only
> account for throttling caused by the cgroup's own bandwidth limit.
> 
> Signed-off-by: Sun Shaojie <sunshaojie@kylinos.cn>
> ---
> Changes in v3:
> - Clarify that the three base CPU usage stats include descendant
>   cgroups.
> - Add a note explaining that the five CFS bandwidth stats are
>   non-hierarchical.
> ---
>  Documentation/admin-guide/cgroup-v2.rst | 23 ++++++++++++++++++++++-
>  1 file changed, 22 insertions(+), 1 deletion(-)

Acked-by: Michal Koutný <mkoutny@suse.com>

Thanks!

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 265 bytes --]

  reply	other threads:[~2026-06-29 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-25 13:07 [PATCH] cgroup/cpu: document cpu.stat.local Sun Shaojie
2026-06-25 14:05 ` Tao Cui
2026-06-26  1:09   ` [PATCH v2] " Sun Shaojie
2026-06-26 16:24     ` Michal Koutný
2026-06-29  6:06       ` [PATCH v3] cgroup/cpu: document cpu.stat.local and clarify cpu.stat behavior Sun Shaojie
2026-06-29 13:49         ` Michal Koutný [this message]
2026-06-29 18:55         ` Tejun Heo

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=akJ37sqf6nOTW9hW@localhost.localdomain \
    --to=mkoutny@suse.com \
    --cc=cgroups@vger.kernel.org \
    --cc=corbet@lwn.net \
    --cc=cui.tao@linux.dev \
    --cc=hannes@cmpxchg.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=skhan@linuxfoundation.org \
    --cc=sunshaojie@kylinos.cn \
    --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.