From: Peter Zijlstra <peterz@infradead.org>
To: Valentin Schneider <valentin.schneider@arm.com>
Cc: linux-kernel@vger.kernel.org, mingo@kernel.org,
vincent.guittot@linaro.org, morten.rasmussen@arm.com,
Dietmar.Eggemann@arm.com
Subject: Re: [PATCH 4/5] sched/fair: Tune down misfit nohz kicks
Date: Wed, 6 Feb 2019 17:04:13 +0100 [thread overview]
Message-ID: <20190206160413.GK17550@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20190117153411.2390-5-valentin.schneider@arm.com>
On Thu, Jan 17, 2019 at 03:34:10PM +0000, Valentin Schneider wrote:
> In
>
> commmit 3b1baa6496e6 ("sched/fair: Add 'group_misfit_task' load-balance type")
>
> we set rq->misfit_task_load whenever the current running task has a
> utilization greater than 80% of rq->cpu_capacity. A non-zero value in
> this field enables misfit load balancing.
>
> However, if the task being looked at is already running on a CPU of
> highest capacity, there's nothing more we can do for it. We can
> currently spot this in update_sd_pick_busiest(), which prevents us
> from selecting a sched_group of group_type == group_misfit_task as the
> busiest group, but we don't do any of that in nohz_balancer_kick().
>
> This means that we could repeatedly kick nohz CPUs when there's no
> improvements in terms of load balance to be done.
>
> Introduce a check_misfit_status() helper that returns true iff there
> is a CPU in the system that could give more CPU capacity to a rq's
> misfit task - IOW, there exists a CPU of higher capacity_orig or the
> rq's CPU is severely pressured by rt/IRQ.
>
> Signed-off-by: Valentin Schneider <valentin.schneider@arm.com>
> +static inline int check_misfit_status(struct rq *rq, struct sched_domain *sd)
> +{
> + return rq->misfit_task_load &&
> + (rq->cpu_capacity_orig < rq->rd->max_cpu_capacity ||
> + check_cpu_capacity(rq, sd));
> +}
> @@ -9527,7 +9539,7 @@ static void nohz_balancer_kick(struct rq *rq)
> if (time_before(now, nohz.next_balance))
> goto out;
>
> - if (rq->nr_running >= 2 || rq->misfit_task_load) {
> + if (rq->nr_running >= 2) {
> flags = NOHZ_KICK_MASK;
> goto out;
> }
> @@ -9561,6 +9573,14 @@ static void nohz_balancer_kick(struct rq *rq)
sd = rcu_dereference(rq->sd);
if (sd) {
if ((rq->cfs.h_nr_running >= 1) &&
check_cpu_capacity(rq, sd)) {
flags = NOHZ_KICK_MASK;
goto unlock;
> }
> }
>
> + sd = rcu_dereference(per_cpu(sd_asym_cpucapacity, cpu));
> + if (sd) {
> + if (check_misfit_status(rq, sd)) {
> + flags = NOHZ_KICK_MASK;
> + goto unlock;
> + }
> + }
So while the exact @sd to use for check_cpu_capacity() likely doesn't
matter; this is a 'implicit' test for actually having asym_capacity.
Fair enough I suppose. However, now that you wrote such a nice comment
for the sd_llc_shared case, these other two cases are sad to not have a
comment.
So how about you add something like:
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -9589,8 +9589,12 @@ static void nohz_balancer_kick(struct rq
sd = rcu_dereference(rq->sd);
if (sd) {
- if ((rq->cfs.h_nr_running >= 1) &&
- check_cpu_capacity(rq, sd)) {
+ /*
+ * If there's a CFS task and the current CPU has reduced
+ * capacity; kick the ILB to see if there's a better CPU to run
+ * on.
+ */
+ if (rq->cfs.h_nr_running >= 1 && check_cpu_capacity(rq, sd)) {
flags = NOHZ_KICK_MASK;
goto unlock;
}
@@ -9598,6 +9602,10 @@ static void nohz_balancer_kick(struct rq
sd = rcu_dereference(per_cpu(sd_asym_cpucapacity, cpu));
if (sd) {
+ /*
+ * When ASYM_CAPACITY; see if there's a higher capacity CPU to
+ * run the misfit task on.
+ */
if (check_misfit_status(rq, sd)) {
flags = NOHZ_KICK_MASK;
goto unlock;
@@ -9606,6 +9614,10 @@ static void nohz_balancer_kick(struct rq
sd = rcu_dereference(per_cpu(sd_asym_packing, cpu));
if (sd) {
+ /*
+ * When ASYM_PACKING; see if there's a more preferred CPU going
+ * idle; in which case, kick the ILB to move tasks around.
+ */
for_each_cpu_and(i, sched_domain_span(sd), nohz.idle_cpus_mask) {
if (sched_asym_prefer(i, cpu)) {
flags = NOHZ_KICK_MASK;
next prev parent reply other threads:[~2019-02-06 16:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-17 15:34 [PATCH 0/5] sched/fair: NOHZ cleanups and misfit improvement Valentin Schneider
2019-01-17 15:34 ` [PATCH 1/5] sched/fair: Use for_each_cpu_and for asym-packing nohz kicks Valentin Schneider
2019-02-11 10:50 ` [tip:sched/core] sched/fair: Simplify nohz_balancer_kick() tip-bot for Valentin Schneider
2019-01-17 15:34 ` [PATCH 2/5] sched/fair: Explain LLC nohz kick condition Valentin Schneider
2019-02-11 10:51 ` [tip:sched/core] " tip-bot for Valentin Schneider
2019-01-17 15:34 ` [PATCH 3/5] sched/fair: Prune nohz_balancer_kick() comment block Valentin Schneider
2019-02-11 10:51 ` [tip:sched/core] sched/fair: Prune, fix and simplify the " tip-bot for Valentin Schneider
2019-01-17 15:34 ` [PATCH 4/5] sched/fair: Tune down misfit nohz kicks Valentin Schneider
2019-02-06 16:04 ` Peter Zijlstra [this message]
2019-02-06 17:25 ` Valentin Schneider
2019-02-07 9:57 ` Peter Zijlstra
2019-01-17 15:34 ` [PATCH 5/5] sched/fair: Skip LLC nohz logic for asymmetric systems Valentin Schneider
2019-02-06 16:14 ` Peter Zijlstra
2019-02-06 17:26 ` Valentin Schneider
2019-02-07 9:56 ` Peter Zijlstra
2019-02-07 11:31 ` Valentin Schneider
2019-02-06 14:33 ` [PATCH 0/5] sched/fair: NOHZ cleanups and misfit improvement Valentin Schneider
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=20190206160413.GK17550@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Dietmar.Eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=morten.rasmussen@arm.com \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.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
Powered by JetHome