[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZJNqRefKRP5mxFaw@slm.duckdns.org>
Date: Wed, 21 Jun 2023 11:23:17 -1000
From: Tejun Heo <tj@...nel.org>
To: Josh Don <joshdon@...gle.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Zefan Li <lizefan.x@...edance.com>,
Johannes Weiner <hannes@...xchg.org>,
Ingo Molnar <mingo@...hat.com>,
Juri Lelli <juri.lelli@...hat.com>,
Vincent Guittot <vincent.guittot@...aro.org>,
Dietmar Eggemann <dietmar.eggemann@....com>,
Steven Rostedt <rostedt@...dmis.org>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Valentin Schneider <vschneid@...hat.com>,
cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
mkoutny@...e.com
Subject: Re: [PATCH v3 2/2] sched: add throttled time stat for throttled
children
On Tue, Jun 20, 2023 at 11:32:47AM -0700, Josh Don wrote:
> We currently export the total throttled time for cgroups that are given
> a bandwidth limit. This patch extends this accounting to also account
> the total time that each children cgroup has been throttled.
>
> This is useful to understand the degree to which children have been
> affected by the throttling control. Children which are not runnable
> during the entire throttled period, for example, will not show any
> self-throttling time during this period.
>
> Expose this in a new interface, 'cpu.stat.local', which is similar to
> how non-hierarchical events are accounted in 'memory.events.local'.
>
> Signed-off-by: Josh Don <joshdon@...gle.com>
Acked-by: Tejun Heo <tj@...nel.org>
Thanks.
--
tejun
Powered by blists - more mailing lists