linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@arm.com>
To: Wanpeng Li <wanpeng.li@linux.intel.com>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/7] sched/deadline: reschedule if stop task slip in after pull operations
Date: Mon, 20 Apr 2015 11:27:22 +0100	[thread overview]
Message-ID: <5534D48A.20304@arm.com> (raw)
In-Reply-To: <1428310399-13489-4-git-send-email-wanpeng.li@linux.intel.com>

Hi,

On 06/04/2015 09:53, Wanpeng Li wrote:
> pull_dl_task can drop (and re-acquire) rq->lock, this means a stop task 
> can slip in, in which case we need to reschedule. This patch add the 
> reschedule when the scenario occurs.
> 

Ok, I guess it can happen. Doesn't RT have the same problem? It seems that
it also has to deal with DL tasks slipping in, right?

Thanks,

- Juri

> Signed-off-by: Wanpeng Li <wanpeng.li@linux.intel.com>
> ---
>  kernel/sched/deadline.c | 16 +++++++++++++++-
>  1 file changed, 15 insertions(+), 1 deletion(-)
> 
> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> index b8b9355..844da0f 100644
> --- a/kernel/sched/deadline.c
> +++ b/kernel/sched/deadline.c
> @@ -1739,7 +1739,13 @@ static void switched_from_dl(struct rq *rq, struct task_struct *p)
>  	if (!task_on_rq_queued(p) || rq->dl.dl_nr_running)
>  		return;
>  
> -	if (pull_dl_task(rq))
> +	/*
> +	 * pull_dl_task() can drop (and re-acquire) rq->lock; this
> +	 * means a stop task can slip in, in which case we need to
> +	 * reschedule.
> +	 */
> +	if (pull_dl_task(rq) ||
> +		(rq->stop && task_on_rq_queued(rq->stop)))
>  		resched_curr(rq);
>  }
>  
> @@ -1786,6 +1792,14 @@ static void prio_changed_dl(struct rq *rq, struct task_struct *p,
>  			pull_dl_task(rq);
>  
>  		/*
> +		 * pull_dl_task() can drop (and re-acquire) rq->lock; this
> +		 * means a stop task can slip in, in which case we need to
> +		 * reschedule.
> +		 */
> +		if (rq->stop && task_on_rq_queued(rq->stop))
> +			resched_curr(rq);
> +
> +		/*
>  		 * If we now have a earlier deadline task than p,
>  		 * then reschedule, provided p is still on this
>  		 * runqueue.
> 


  reply	other threads:[~2015-04-20 10:27 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06  8:53 [PATCH 1/7] sched/deadline: fix try to pull pinned dl tasks in pull algorithm Wanpeng Li
2015-04-06  8:53 ` [PATCH 2/7] sched/deadline: make init_sched_dl_class() __init Wanpeng Li
2015-04-07 13:48   ` Juri Lelli
2015-04-07 23:00     ` Wanpeng Li
2015-04-06  8:53 ` [PATCH 3/7] sched/deadline: reduce rq lock contention by eliminating locking of non-feasible target Wanpeng Li
2015-04-07 13:48   ` Juri Lelli
2015-04-07 22:57     ` Wanpeng Li
2015-04-06  8:53 ` [PATCH 4/7] sched/deadline: reschedule if stop task slip in after pull operations Wanpeng Li
2015-04-20 10:27   ` Juri Lelli [this message]
2015-04-20 22:59     ` Wanpeng Li
2015-04-20 23:02       ` Wanpeng Li
2015-04-21  8:22         ` Juri Lelli
2015-04-06  8:53 ` [PATCH 5/7] sched/deadline: drop duplicate init_sched_dl_class declaration Wanpeng Li
2015-04-08  8:47   ` Juri Lelli
2015-04-08  8:33     ` Wanpeng Li
2015-04-06  8:53 ` [PATCH 6/7] sched/deadline: depend on clearing throttled status in replenish_dl_entity Wanpeng Li
2015-04-21  8:16   ` Juri Lelli
2015-04-21  8:10     ` Wanpeng Li
2015-04-06  8:53 ` [PATCH 7/7] sched/rt: reschedule if stop/dl task slip in after pull operations Wanpeng Li
2015-04-14 23:10 ` [PATCH 1/7] sched/deadline: fix try to pull pinned dl tasks in pull algorithm Wanpeng Li
2015-04-27  9:42 ` Wanpeng Li
2015-05-06  7:11   ` Wanpeng Li

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=5534D48A.20304@arm.com \
    --to=juri.lelli@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=wanpeng.li@linux.intel.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;
as well as URLs for NNTP newsgroup(s).