From: Valentin Schneider <valentin.schneider@arm.com>
To: Vincent Guittot <vincent.guittot@linaro.org>
Cc: Peng Liu <iwtbavbm@gmail.com>,
dietmar.eggemann@arm.com, mingo@redhat.com, peterz@infradead.org,
juri.lelli@redhat.com, rostedt@goodmis.org, bsegall@google.com,
mgorman@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched/fair: Fix nohz.next_balance update
Date: Wed, 06 May 2020 11:29:10 +0100 [thread overview]
Message-ID: <jhjftcd1hmx.mognet@arm.com> (raw)
In-Reply-To: <20200505142711.GA12952@vingu-book>
On 05/05/20 15:27, Vincent Guittot wrote:
> So I would be in favor of something as simple as :
>
> diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
> index 04098d678f3b..e028bc1c4744 100644
> --- a/kernel/sched/fair.c
> +++ b/kernel/sched/fair.c
> @@ -10457,6 +10457,14 @@ static bool _nohz_idle_balance(struct rq *this_rq, unsigned int flags,
> }
> }
>
> + /*
> + * next_balance will be updated only when there is a need.
> + * When the CPU is attached to null domain for ex, it will not be
> + * updated.
> + */
> + if (likely(update_next_balance))
> + nohz.next_balance = next_balance;
> +
> /* Newly idle CPU doesn't need an update */
> if (idle != CPU_NEWLY_IDLE) {
> update_blocked_averages(this_cpu);
> @@ -10477,14 +10485,6 @@ static bool _nohz_idle_balance(struct rq *this_rq, unsigned int flags,
> if (has_blocked_load)
> WRITE_ONCE(nohz.has_blocked, 1);
>
> - /*
> - * next_balance will be updated only when there is a need.
> - * When the CPU is attached to null domain for ex, it will not be
> - * updated.
> - */
> - if (likely(update_next_balance))
> - nohz.next_balance = next_balance;
> -
> return ret;
> }
>
But then we may skip an update if we goto abort, no? Imagine we have just
NOHZ_STATS_KICK, so we don't call any rebalance_domains(), and then as we
go through the last NOHZ CPU in the loop we hit need_resched(). We would
end in the abort part without any update to nohz.next_balance, despite
having accumulated relevant data in the local next_balance variable.
Also note that in this case, nohz_idle_balance() will still return true.
If we rip out just the one update we need from rebalance_domains(), then
perhaps we could go with what Peng was initially suggesting? i.e. something
like the below.
---
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 46b7bd41573f..0a292e0a0731 100644
--- a/kernel/sched/fair.c
+++ b/kernel/sched/fair.c
@@ -9934,22 +9934,8 @@ static void rebalance_domains(struct rq *rq, enum cpu_idle_type idle)
* When the cpu is attached to null domain for ex, it will not be
* updated.
*/
- if (likely(update_next_balance)) {
+ if (likely(update_next_balance))
rq->next_balance = next_balance;
-
-#ifdef CONFIG_NO_HZ_COMMON
- /*
- * If this CPU has been elected to perform the nohz idle
- * balance. Other idle CPUs have already rebalanced with
- * nohz_idle_balance() and nohz.next_balance has been
- * updated accordingly. This CPU is now running the idle load
- * balance for itself and we need to update the
- * nohz.next_balance accordingly.
- */
- if ((idle == CPU_IDLE) && time_after(nohz.next_balance, rq->next_balance))
- nohz.next_balance = rq->next_balance;
-#endif
- }
}
static inline int on_null_domain(struct rq *rq)
@@ -10315,6 +10301,11 @@ static bool _nohz_idle_balance(struct rq *this_rq, unsigned int flags,
if (flags & NOHZ_BALANCE_KICK)
rebalance_domains(this_rq, CPU_IDLE);
+ if (time_after(next_balance, this_rq->next_balance)) {
+ next_balance = this_rq->next_balance;
+ update_next_balance = 1;
+ }
+
WRITE_ONCE(nohz.next_blocked,
now + msecs_to_jiffies(LOAD_AVG_PERIOD));
@@ -10551,6 +10542,17 @@ static __latent_entropy void run_rebalance_domains(struct softirq_action *h)
/* normal load balance */
update_blocked_averages(this_rq->cpu);
rebalance_domains(this_rq, idle);
+
+#ifdef CONFIG_NO_HZ_COMMON
+ /*
+ * NOHZ idle CPUs will be rebalanced with nohz_idle_balance() and thus
+ * nohz.next_balance will be updated accordingly. If there was no NOHZ
+ * kick, then we just need to update nohz.next_balance wrt *this* CPU.
+ */
+ if ((idle == CPU_IDLE) &&
+ time_after(nohz.next_balance, this_rq->next_balance))
+ nohz.next_balance = this_rq->next_balance;
+#endif
}
/*
---
next prev parent reply other threads:[~2020-05-06 10:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 8:34 [PATCH] sched/fair: Fix nohz.next_balance update Peng Liu
2020-05-04 0:10 ` Valentin Schneider
2020-05-05 12:36 ` Peng Liu
2020-05-04 15:17 ` Vincent Guittot
2020-05-04 15:48 ` Valentin Schneider
2020-05-04 16:05 ` Dietmar Eggemann
2020-05-05 13:40 ` Peng Liu
2020-05-05 14:27 ` Vincent Guittot
2020-05-05 15:16 ` Peng Liu
2020-05-05 15:43 ` Vincent Guittot
2020-05-05 16:08 ` Peng Liu
2020-05-06 10:29 ` Valentin Schneider [this message]
2020-05-06 13:45 ` Vincent Guittot
2020-05-06 16:02 ` Valentin Schneider
2020-05-06 16:56 ` Vincent Guittot
2020-05-06 20:21 ` Valentin Schneider
2020-05-07 12:41 ` Peng Liu
2020-05-07 12:53 ` Vincent Guittot
2020-05-08 13:01 ` Peng Liu
2020-05-08 15:31 ` Vincent Guittot
2020-05-06 10:28 ` 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=jhjftcd1hmx.mognet@arm.com \
--to=valentin.schneider@arm.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=iwtbavbm@gmail.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--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