From: Juri Lelli <juri.lelli@arm.com>
To: xlpang@redhat.com
Cc: peterz@infradead.org, rostedt@goodmis.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
luca.abeni@unitn.it
Subject: Re: [PATCH v4] sched/deadline: remove useless param from setup_new_dl_entity
Date: Fri, 5 Aug 2016 11:13:14 +0100 [thread overview]
Message-ID: <20160805101314.GD28125@e106622-lin> (raw)
In-Reply-To: <57918BEF.2090400@redhat.com>
On 22/07/16 10:58, Xunlei Pang wrote:
> On 2016/07/21 at 22:46, Juri Lelli wrote:
[...]
> > @@ -1734,9 +1724,11 @@ static void switched_to_dl(struct rq *rq, struct task_struct *p)
> > if (task_on_rq_queued(p)) {
> > /*
> > * If p is not queued we will update its parameters at next
> > - * wakeup.
> > + * wakeup. If p is dl_boosted we already updated its params in
> > + * rt_mutex_setprio()->enqueue_task(..., ENQUEUE_REPLENISH).
> > */
> > - if (dl_time_before(p->dl.deadline, rq_clock(rq)))
> > + if (dl_time_before(p->dl.deadline, rq_clock(rq)) &&
> > + !p->dl.dl_boosted)
>
> Hi Juri,
>
> It looks good to me, only one question:
> For on_rq boosted to deadline, p->dl.deadline has been updated after rq_lock(rq) by
> rt_mutex_setprio()->enqueue_task(..., ENQUEUE_REPLENISH) and no rq clock update
> afterwards, so dl_time_before() will be false, seems p->dl.dl_boosted check is needless.
>
Right. I removed it and posted v5. Please have a look.
Best,
- Juri
prev parent reply other threads:[~2016-08-05 10:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-13 10:58 [PATCH v4] sched/deadline: remove useless param from setup_new_dl_entity Juri Lelli
2016-07-15 10:39 ` Xunlei Pang
2016-07-18 13:04 ` Juri Lelli
2016-07-18 13:37 ` Xunlei Pang
2016-07-21 14:21 ` Juri Lelli
2016-07-21 14:36 ` Juri Lelli
2016-07-21 14:46 ` Juri Lelli
2016-07-22 2:58 ` Xunlei Pang
2016-08-05 10:13 ` 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=20160805101314.GD28125@e106622-lin \
--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=rostedt@goodmis.org \
--cc=xlpang@redhat.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).