All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincent Guittot <vincent.guittot@linaro.org>
To: Vincent Donnefort <vincent.donnefort@arm.com>
Cc: Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Juri Lelli <juri.lelli@redhat.com>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>,
	Valentin Schneider <valentin.schneider@arm.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/2] sched/rt: Fix RT utilization tracking during policy change
Date: Mon, 21 Jun 2021 14:03:43 +0200	[thread overview]
Message-ID: <CAKfTPtD5bn-DnOZOcYfesFm+mP7urCiaeEsF+gd-e=jtpCK96A@mail.gmail.com> (raw)
In-Reply-To: <1624271872-211872-2-git-send-email-vincent.donnefort@arm.com>

On Mon, 21 Jun 2021 at 12:39, Vincent Donnefort
<vincent.donnefort@arm.com> wrote:
>
> RT keeps track of the utilization on a per-rq basis with the structure
> avg_rt. This utilization is updated during task_tick_rt(),
> put_prev_task_rt() and set_next_task_rt(). However, when the current
> running task changes its policy, set_next_task_rt() which would usually
> take care of updating the utilization when the rq starts running RT tasks,
> will not see a such change, leaving the avg_rt structure outdated. When
> that very same task will be dequeued later, put_prev_task_rt() will then
> update the utilization, based on a wrong last_update_time, leading to a
> huge spike in the RT utilization signal.
>
> The signal would eventually recover from this issue after few ms. Even if
> no RT tasks are run, avg_rt is also updated in __update_blocked_others().
> But as the CPU capacity depends partly on the avg_rt, this issue has
> nonetheless a significant impact on the scheduler.
>
> Fix this issue by ensuring a load update when a running task changes
> its policy to RT.
>
> Fixes: 371bf427 ("sched/rt: Add rt_rq utilization tracking")
> Signed-off-by: Vincent Donnefort <vincent.donnefort@arm.com>

Reviewed-by: Vincent Guittot <vincent.guittot@linaro.org>

>
> diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
> index a525447..3daf42a 100644
> --- a/kernel/sched/rt.c
> +++ b/kernel/sched/rt.c
> @@ -2341,13 +2341,20 @@ void __init init_sched_rt_class(void)
>  static void switched_to_rt(struct rq *rq, struct task_struct *p)
>  {
>         /*
> -        * If we are already running, then there's nothing
> -        * that needs to be done. But if we are not running
> -        * we may need to preempt the current running task.
> -        * If that current running task is also an RT task
> +        * If we are running, update the avg_rt tracking, as the running time
> +        * will now on be accounted into the latter.
> +        */
> +       if (task_current(rq, p)) {
> +               update_rt_rq_load_avg(rq_clock_pelt(rq), rq, 0);
> +               return;
> +       }
> +
> +       /*
> +        * If we are not running we may need to preempt the current
> +        * running task. If that current running task is also an RT task
>          * then see if we can move to another run queue.
>          */
> -       if (task_on_rq_queued(p) && rq->curr != p) {
> +       if (task_on_rq_queued(p)) {
>  #ifdef CONFIG_SMP
>                 if (p->nr_cpus_allowed > 1 && rq->rt.overloaded)
>                         rt_queue_push_tasks(rq);
> --
> 2.7.4
>

  reply	other threads:[~2021-06-21 12:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-21 10:37 [PATCH v2 0/2] Fix RT/DL utilization during policy change Vincent Donnefort
2021-06-21 10:37 ` [PATCH v2 1/2] sched/rt: Fix RT utilization tracking " Vincent Donnefort
2021-06-21 12:03   ` Vincent Guittot [this message]
2021-06-23  8:19   ` [tip: sched/core] " tip-bot2 for Vincent Donnefort
2021-06-21 10:37 ` [PATCH v2 2/2] sched/rt: Fix Deadline " Vincent Donnefort
2021-06-23  8:19   ` [tip: sched/core] " tip-bot2 for Vincent Donnefort
2021-06-22 13:16 ` [PATCH v2 0/2] Fix RT/DL utilization " Peter Zijlstra

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='CAKfTPtD5bn-DnOZOcYfesFm+mP7urCiaeEsF+gd-e=jtpCK96A@mail.gmail.com' \
    --to=vincent.guittot@linaro.org \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=valentin.schneider@arm.com \
    --cc=vincent.donnefort@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.