From: luca abeni <luca.abeni@unitn.it>
To: Xunlei Pang <xpang@redhat.com>
Cc: Juri Lelli <juri.lelli@arm.com>,
peterz@infradead.org, rostedt@goodmis.org,
linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [PATCH v3] sched/deadline: remove useless param from setup_new_dl_entity
Date: Mon, 11 Jul 2016 11:22:57 +0200 [thread overview]
Message-ID: <20160711112257.393d5614@utopia> (raw)
In-Reply-To: <578355D4.9080007@redhat.com>
On Mon, 11 Jul 2016 16:16:20 +0800
Xunlei Pang <xpang@redhat.com> wrote:
> On 2016/07/11 at 16:01, luca abeni wrote:
> > Hello,
> >
> > On Mon, 11 Jul 2016 13:03:56 +0800
> > Xunlei Pang <xpang@redhat.com> wrote:
> >
> >> On 2016/07/08 at 19:28, Juri Lelli wrote:
> > [...]
> >>> @@ -363,6 +364,15 @@ static inline void setup_new_dl_entity(struct
> >>> sched_dl_entity *dl_se, return;
> >>>
> >>> /*
> >>> + * Use the scheduling parameters of the top pi-waiter
> >>> task,
> >>> + * if we have one from which we can inherit a deadline.
> >>> + */
> >>> + if (dl_se->dl_boosted &&
> >>> + (pi_task = rt_mutex_get_top_task(dl_task_of(dl_se)))
> >>> &&
> >>> + dl_prio(pi_task->normal_prio))
> >>> + pi_se = &pi_task->dl;
> >>> +
> >>> + /*
> >>> * We use the regular wall clock time to set deadlines in
> >>> the
> >>> * future; in fact, we must consider execution overheads
> >>> (time
> >>> * spent on hardirq context, etc.).
> >>> @@ -1721,7 +1731,7 @@ static void switched_from_dl(struct rq *rq,
> >>> struct task_struct *p) static void switched_to_dl(struct rq *rq,
> >>> struct task_struct *p) {
> >>> if (dl_time_before(p->dl.deadline, rq_clock(rq)))
> >>> - setup_new_dl_entity(&p->dl, &p->dl);
> >>> + setup_new_dl_entity(&p->dl);
> >> I'm curious why we even call setup_new_dl_entity() for non-queued
> >> cases? It seems more reasonable to do it when it really gets
> >> queued. We can see that enqueue_task_dl()->update_dl_entity() also
> >> has the same update logic as switched_to_dl().
> > I wondered the same when removing the dl_new field from
> > sched_dl_entity... But then I realised that enqueue_dl_entity() does
> > not always invoke update_dl_entity() or replenish_dl_entity()... For
> > example, when a task switches from SCHED_OTHER (or RT) to -deadline
> > due to sched_setattr() (or similar) these functions are not
> > invoked.
>
> Yeah, but for wake-up cases it does, as ENQUEUE_WAKEUP is set.
> What I meant is, can we only update for queued tasks in
> switched_to_dl()?
Uhm... Looking at this code again, I am not sure anymore about it...
(switched_to_dl() is invoked after enqueue enqueue_task_dl()?)
Maybe the best thing to do is to move the
"if (dl_time_before(p->dl.deadline, rq_clock(rq)))"
check in enqueue_dl_entity() (Juri, what do you think)? I'll try this
approach in the next days.
Thanks,
Luca
next prev parent reply other threads:[~2016-07-11 9:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 11:28 [PATCH v3] sched/deadline: remove useless param from setup_new_dl_entity Juri Lelli
2016-07-11 5:03 ` Xunlei Pang
2016-07-11 8:01 ` luca abeni
2016-07-11 8:16 ` Xunlei Pang
2016-07-11 9:22 ` luca abeni [this message]
2016-07-12 8:42 ` 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=20160711112257.393d5614@utopia \
--to=luca.abeni@unitn.it \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=xpang@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