public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>,
	linux-kernel@vger.kernel.org, tglx@linutronix.de,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] kernel/sched/rt: Add a rescheduling point
Date: Wed, 25 Jan 2017 13:16:24 +0100	[thread overview]
Message-ID: <20170125121624.GM6500@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20170124144006.29821-1-bigeasy@linutronix.de>

On Tue, Jan 24, 2017 at 03:40:06PM +0100, Sebastian Andrzej Siewior wrote:
> Since the change in commit fd7a4bed1835 ("sched, rt: Convert
> switched_{from, to}_rt() / prio_changed_rt() to balance callbacks") we
> don't reschedule a task under certain circumstances:
> 
> Lets say taskA, SCHED_OTHER, is running on CPU0 (and it may run only on
> CPU0) and holds a PI lock. This task is removed from the CPU because it
> used up its time slice and another SCHED_OTHER task is running. TaskB on
> CPU1 runs at RT priority and asks for the lock owned by taskA. This
> results in a priority boost for taskA. TaskB goes to sleep until the
> lock has been made available. TaskA is already runable (but not active)
> so it receives no wake up.
> The reality now is that taskA gets on the CPU once the scheduler decides
> to remove the current task despite the fact that a high priority task is
> enqueued and waiting. This may take a long time.
> The desired behaviour is that CPU0 immediately reschedules after the
> priority boost which made taskA the task with the lowest priority.
> 
> Fixes: fd7a4bed1835 ("sched, rt: Convert switched_{from, to}_rt() /
> 		     prio_changed_rt() to balance callbacks")
> Suggested-by: Peter Zijlstra <peterz@infradead.org>
> Signed-off-by: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> ---
>  kernel/sched/rt.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
> index 88254be118b0..cdba8d58dbc5 100644
> --- a/kernel/sched/rt.c
> +++ b/kernel/sched/rt.c
> @@ -2198,10 +2198,10 @@ static void switched_to_rt(struct rq *rq, struct task_struct *p)
>  #ifdef CONFIG_SMP
>  		if (tsk_nr_cpus_allowed(p) > 1 && rq->rt.overloaded)
>  			queue_push_tasks(rq);
> -#else
> +		else

I killed that "else" as well, because the queue_push_tasks() can fail to
actually push the task, in which case we'd still miss the preemption.

> +#endif /* CONFIG_SMP */
>  		if (p->prio < rq->curr->prio)
>  			resched_curr(rq);
> -#endif /* CONFIG_SMP */
>  	}
>  }
>  
> -- 
> 2.11.0
> 

  parent reply	other threads:[~2017-01-25 12:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24 14:40 [PATCH] kernel/sched/rt: Add a rescheduling point Sebastian Andrzej Siewior
2017-01-24 14:43 ` Sebastian Andrzej Siewior
2017-01-24 15:17   ` Peter Zijlstra
2017-01-25 12:16 ` Peter Zijlstra [this message]
2017-01-30 11:57 ` [tip:sched/core] sched/rt: Add a missing " tip-bot for Sebastian Andrzej Siewior

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=20170125121624.GM6500@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=bigeasy@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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