From: Steven Rostedt <rostedt@goodmis.org>
To: Juri Lelli <juri.lelli@arm.com>
Cc: peterz@infradead.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, luca.abeni@unitn.it
Subject: Re: [PATCH v2] sched/deadline: remove useless param from setup_new_dl_entity
Date: Tue, 5 Jul 2016 12:47:40 -0400 [thread overview]
Message-ID: <20160705124740.34a3fbb5@gandalf.local.home> (raw)
In-Reply-To: <20160705143933.GJ17689@e106622-lin>
On Tue, 5 Jul 2016 15:39:33 +0100
Juri Lelli <juri.lelli@arm.com> wrote:
return;
> > >
> > > /*
> > > + * Use the scheduling parameters of the top pi-waiter task,
> > > + * if we have one from which we can inherit a deadline.
> > > + */
> > > + if (pi_task && dl_se->dl_boosted && dl_prio(pi_task->normal_prio))
> > > + pi_se = &pi_task->dl;
> > > +
> >
> > OK, I'm micro-optimizing now, but hey, isn't this a fast path?
> >
> > What about changing the above to:
> >
> > struct task_struct *pi_task;
> > [...]
> >
> > if (dl_se->dl_boosted && dl_prio(pi_task->normal_prio &&
> ^
> OK, we need to reorder these two
> V
> > (pi_task = rt_mutex_get_top_task(dl_task_of(dl_se)))
> > pe_se = &pi_task->dl;
Opps, you're right.
> >
> > This way we don't need to do any work of looking at
> > rt_mutex_get_top_task() for the normal case.
> >
>
> But, yes. Looks good to me. I'll shoot a v3 ASAP.
I have to ask, should there be any check if the dl_se has a shorter
deadline than the pi one?
-- Steve
next prev parent reply other threads:[~2016-07-05 16:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 19:07 Juri Lelli
2016-07-04 9:03 ` luca abeni
2016-07-04 9:28 ` Juri Lelli
2016-07-05 7:37 ` Wanpeng Li
2016-07-05 8:52 ` Juri Lelli
2016-07-05 14:20 ` Steven Rostedt
2016-07-05 14:39 ` Juri Lelli
2016-07-05 16:47 ` Steven Rostedt [this message]
2016-07-05 16:58 ` Juri Lelli
2016-07-06 8:44 ` luca abeni
2016-07-07 8:39 ` Juri Lelli
2016-07-07 13:47 ` Steven Rostedt
2016-07-08 11:32 ` Juri Lelli
2016-07-06 8:46 ` luca abeni
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=20160705124740.34a3fbb5@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=juri.lelli@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.abeni@unitn.it \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
/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
all inboxes | Powered by JetHome®