All of lore.kernel.org
 help / color / mirror / Atom feed
From: Juri Lelli <juri.lelli@arm.com>
To: Luca Abeni <luca.abeni@unitn.it>, linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Wanpeng Li <wanpeng.li@linux.intel.com>
Subject: Re: [PATCH] Fix migration of SCHED_DEADLINE tasks
Date: Thu, 15 Oct 2015 17:40:19 +0100	[thread overview]
Message-ID: <561FD6F3.4090209@arm.com> (raw)
In-Reply-To: <1444907357-13114-1-git-send-email-luca.abeni@unitn.it>

Hi Luca,

On 15/10/15 12:09, Luca Abeni wrote:
> Commit 9d5142624256 ("sched/deadline: Reduce rq lock contention by
> eliminating locking of non-feasible target") broke select_task_rq_dl()
> and find_lock_later_rq(), because it introduced a comparison between
> the local task's deadline and dl.earliest_dl.curr of the remote queue.
> However, if the remote runqueue does not contain any SCHED_DEADLINE
> task its earliest_dl.curr is 0 (always smaller than the deadline of
> the local task) and the remote runqueue is not selected for pushing.
> As a result, if an application creates multiple SCHED_DEADLINE threads,
> they will never be pushed to runqueues that do not already contain
> SCHED_DEADLINE tasks.
> This patches fixes the issue by checking if dl.earliest_dl.curr == 0.
> 
> Signed-off-by: Luca Abeni <luca.abeni@unitn.it>
> ---
>  kernel/sched/deadline.c | 8 +++++---
>  1 file changed, 5 insertions(+), 3 deletions(-)
> 
> diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> index fc8f010..0d86d60 100644
> --- a/kernel/sched/deadline.c
> +++ b/kernel/sched/deadline.c
> @@ -1066,8 +1066,9 @@ select_task_rq_dl(struct task_struct *p, int cpu, int sd_flag, int flags)
>  		int target = find_later_rq(p);
>  
>  		if (target != -1 &&
> -				dl_time_before(p->dl.deadline,
> -					cpu_rq(target)->dl.earliest_dl.curr))
> +				(dl_time_before(p->dl.deadline,
> +					cpu_rq(target)->dl.earliest_dl.curr) ||
> +				(cpu_rq(target)->dl.earliest_dl.curr == 0)))

Can't we actually use dl.dl_nr_running here and below, so
that we won't incur any wraparound problem?

Thanks,

- Juri

>  			cpu = target;
>  	}
>  	rcu_read_unlock();
> @@ -1417,7 +1418,8 @@ static struct rq *find_lock_later_rq(struct task_struct *task, struct rq *rq)
>  
>  		later_rq = cpu_rq(cpu);
>  
> -		if (!dl_time_before(task->dl.deadline,
> +		if (later_rq->dl.earliest_dl.curr &&
> +			!dl_time_before(task->dl.deadline,
>  					later_rq->dl.earliest_dl.curr)) {
>  			/*
>  			 * Target rq has tasks of equal or earlier deadline,
> 


  reply	other threads:[~2015-10-15 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-15 11:09 [PATCH] Fix migration of SCHED_DEADLINE tasks Luca Abeni
2015-10-15 16:40 ` Juri Lelli [this message]
2015-10-15 20:10   ` Luca Abeni
2015-10-16  8:03   ` Luca Abeni
2015-10-16  8:51     ` Juri Lelli

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=561FD6F3.4090209@arm.com \
    --to=juri.lelli@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.abeni@unitn.it \
    --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 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.