public inbox for linux-kernel@vger.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: Fri, 16 Oct 2015 09:51:49 +0100	[thread overview]
Message-ID: <5620BAA5.5010807@arm.com> (raw)
In-Reply-To: <5620AF64.4050208@unitn.it>

Hi,

On 16/10/15 09:03, Luca Abeni wrote:
> On 10/15/2015 06:40 PM, Juri Lelli wrote:
>> 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()
> [...]
>>> -                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?
> Ok, I tested the patch with dl.dl_nr_running and if works for me...
> 
> I am going to send the updated patch in few minutes.
> 

Thanks!

> BTW, should we also use "dl_rq->dl_nr_running == 0" instead of
> "dl_rq->earliest_dl.curr == 0" in inc_dl_deadline(), and remove the
> comment from init_dl_rq()? If you think it is a good idea, I'll test this
> additional change and send a patch in next week.
> 

Yeah, it seems we need that fix too.

Best,

- Juri


      reply	other threads:[~2015-10-16  8:51 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
2015-10-15 20:10   ` Luca Abeni
2015-10-16  8:03   ` Luca Abeni
2015-10-16  8:51     ` Juri Lelli [this message]

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=5620BAA5.5010807@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox