From: bsegall@google.com
To: Liangyan <liangyan.peng@linux.alibaba.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, shanpeic@linux.alibaba.com,
xlpang@linux.alibaba.com
Subject: Re: [PATCH] sched/fair: don't assign runtime for throttled cfs_rq
Date: Fri, 23 Aug 2019 13:00:43 -0700 [thread overview]
Message-ID: <xm26d0gvirdg.fsf@bsegall-linux.svl.corp.google.com> (raw)
In-Reply-To: <20190814180021.165389-1-liangyan.peng@linux.alibaba.com> (Liangyan's message of "Thu, 15 Aug 2019 02:00:21 +0800")
Liangyan <liangyan.peng@linux.alibaba.com> writes:
> do_sched_cfs_period_timer() will refill cfs_b runtime and call
> distribute_cfs_runtime() to unthrottle cfs_rq, sometimes cfs_b->runtime
> will allocate all quota to one cfs_rq incorrectly.
> This will cause other cfs_rq can't get runtime and will be throttled.
> We find that one throttled cfs_rq has non-negative
> cfs_rq->runtime_remaining and cause an unexpetced cast from s64 to u64
> in snippet: distribute_cfs_runtime() {
> runtime = -cfs_rq->runtime_remaining + 1; }.
> This cast will cause that runtime will be a large number and
> cfs_b->runtime will be subtracted to be zero at last.
>
> This commit prevents cfs_rq to be assgined new runtime if it has been
> throttled to avoid the above incorrect type cast.
>
> Signed-off-by: Liangyan <liangyan.peng@linux.alibaba.com>
Could you mention in the message that this a throttled cfs_rq can have
account_cfs_rq_runtime called on it because it is throttled before
idle_balance, and the idle_balance calls update_rq_clock to add time
that is accounted to the task.
I think this solution is less risky than unthrottling
in this area, so other than that:
Reviewed-by: Ben Segall <bsegall@google.com>
> ---
> kernel/sched/fair.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 81fd8a2a605b..b14d67d28138 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -4068,6 +4068,8 @@ static void __account_cfs_rq_runtime(struct cfs_rq *cfs_rq, u64 delta_exec)
> if (likely(cfs_rq->runtime_remaining > 0))
> return;
>
> + if (cfs_rq->throttled)
> + return;
> /*
> * if we're unable to extend our runtime we resched so that the active
> * hierarchy can be throttled
next prev parent reply other threads:[~2019-08-23 20:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-14 18:00 Liangyan
2019-08-15 16:36 ` Valentin Schneider
[not found] ` <7C1833A8-27A4-4755-9B1E-335C20207A66@linux.alibaba.com>
2019-08-16 14:02 ` Valentin Schneider
2019-08-16 14:31 ` Valentin Schneider
[not found] ` <02BC41EE-6653-4473-91D4-CDEE53D8703D@linux.alibaba.com>
2019-08-16 17:19 ` Valentin Schneider
2019-08-19 17:34 ` Valentin Schneider
2019-08-20 10:54 ` [PATCH] sched/fair: Add missing unthrottle_cfs_rq() Valentin Schneider
2019-08-22 9:21 ` Peter Zijlstra
2019-08-22 17:43 ` bsegall
2019-08-22 18:48 ` bsegall
2019-08-22 20:40 ` Valentin Schneider
2019-08-22 21:10 ` Valentin Schneider
2019-08-23 7:22 ` Liangyan
2019-08-23 20:00 ` bsegall [this message]
2019-08-23 23:19 ` [PATCH] sched/fair: don't assign runtime for throttled cfs_rq Valentin Schneider
2019-08-26 17:38 ` bsegall
2019-08-27 2:45 ` Liangyan
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=xm26d0gvirdg.fsf@bsegall-linux.svl.corp.google.com \
--to=bsegall@google.com \
--cc=liangyan.peng@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=shanpeic@linux.alibaba.com \
--cc=xlpang@linux.alibaba.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
Powered by JetHome