From: 王贇 <yun.wang@linux.alibaba.com>
To: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] tg: show the sum wait time of an task group
Date: Tue, 17 Jul 2018 11:28:40 +0800 [thread overview]
Message-ID: <4abd1bae-dc1e-3a13-40d4-c6c73ecc07b1@linux.alibaba.com> (raw)
In-Reply-To: <ff7dae3b-e5f9-7157-1caa-ff02c6b23dc1@linux.alibaba.com>
Hi, folks
On 2018/7/4 上午11:27, 王贇 wrote:
> Although we can rely on cpuacct to present the cpu usage of task
> group, it is hard to tell how intense the competition is between
> these groups on cpu resources.
>
> Monitoring the wait time of each process or sched_debug could cost
> too much, and there is no good way to accurately represent the
> conflict with these info, we need the wait time on group dimension.
>
> Thus we introduced group's wait_sum represent the conflict between
> task groups, which is simply sum the wait time of group's cfs_rq.
>
> The 'cpu.stat' is modified to show the statistic, like:
>
> nr_periods 0
> nr_throttled 0
> throttled_time 0
> wait_sum 2035098795584
>
> Now we can monitor the changing on wait_sum to tell how suffering
> a task group is in the fight of cpu resources.
>
> For example:
> (wait_sum - last_wait_sum) * 100 / (nr_cpu * period_ns) == X%
>
> means the task group paid X percentage of period on waiting
> for the cpu.
Any comments please?
Regards,
Michael Wang
>
> Signed-off-by: Michael Wang <yun.wang@linux.alibaba.com>
> ---
>
> Since v1:
> Use schedstat_val to avoid compile error
> Check and skip root_task_group
>
> kernel/sched/core.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 78d8fac..80ab995 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -6781,6 +6781,8 @@ static int __cfs_schedulable(struct task_group *tg, u64 period, u64 quota)
>
> static int cpu_cfs_stat_show(struct seq_file *sf, void *v)
> {
> + int i;
> + u64 ws = 0;
> struct task_group *tg = css_tg(seq_css(sf));
> struct cfs_bandwidth *cfs_b = &tg->cfs_bandwidth;
>
> @@ -6788,6 +6790,12 @@ static int cpu_cfs_stat_show(struct seq_file *sf, void *v)
> seq_printf(sf, "nr_throttled %d\n", cfs_b->nr_throttled);
> seq_printf(sf, "throttled_time %llu\n", cfs_b->throttled_time);
>
> + if (schedstat_enabled() && tg != &root_task_group) {
> + for_each_possible_cpu(i)
> + ws += schedstat_val(tg->se[i]->statistics.wait_sum);
> + seq_printf(sf, "wait_sum %llu\n", ws);
> + }
> +
> return 0;
> }
> #endif /* CONFIG_CFS_BANDWIDTH */
next prev parent reply other threads:[~2018-07-17 3:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 7:29 [RFC PATCH] tg: count " 王贇
2018-07-02 12:03 ` Peter Zijlstra
2018-07-03 2:10 ` 王贇
2018-07-03 5:42 ` [PATCH] tg: show " 王贇
2018-07-04 3:27 ` [PATCH v2] " 王贇
2018-07-09 9:12 ` 王贇
2018-07-17 3:28 ` 王贇 [this message]
2018-07-23 9:31 ` Peter Zijlstra
2018-07-23 12:32 ` 王贇
2018-07-23 13:31 ` [PATCH v3] " 王贇
2018-07-25 14:23 ` [tip:sched/core] sched/debug: Show the sum wait time of a " tip-bot for Yun Wang
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=4abd1bae-dc1e-3a13-40d4-c6c73ecc07b1@linux.alibaba.com \
--to=yun.wang@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 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®