public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Byungchul Park <byungchul.park@lge.com>
To: Juri Lelli <juri.lelli@arm.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	peterz@infradead.org, mingo@kernel.org,
	linux-kernel@vger.kernel.org, juri.lelli@gmail.com,
	kernel-team@lge.com, Luca Abeni <luca.abeni@santannapisa.it>
Subject: Re: [PATCH] sched/deadline: Remove unnecessary condition in push_dl_task()
Date: Thu, 16 Feb 2017 11:17:58 +0900	[thread overview]
Message-ID: <20170216021758.GS16086@X58A-UD3R> (raw)
In-Reply-To: <20170215144503.GG1368@e106622-lin>

On Wed, Feb 15, 2017 at 02:45:03PM +0000, Juri Lelli wrote:
> On 15/02/17 09:25, Steven Rostedt wrote:
> > On Wed, 15 Feb 2017 10:47:49 +0000
> > Juri Lelli <juri.lelli@arm.com> wrote:
> > 
> > > [+Steve, Luca]
> > > 
> > > Hi,
> > > 
> > > On 15/02/17 14:11, Byungchul Park wrote:
> > > > Once pick_next_pushable_dl_task(rq) return a task, it guarantees that
> > > > the task's cpu is rq->cpu, so task_cpu(next_task) is always rq->cpu if
> > > > task == next_task. Remove a redundant condition and make code simpler.
> > > > 
> > > > Signed-off-by: Byungchul Park <byungchul.park@lge.com>
> > > > ---
> > > >  kernel/sched/deadline.c | 2 +-
> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > > 
> > > > diff --git a/kernel/sched/deadline.c b/kernel/sched/deadline.c
> > > > index 27737f3..ad8d577 100644
> > > > --- a/kernel/sched/deadline.c
> > > > +++ b/kernel/sched/deadline.c
> > > > @@ -1483,7 +1483,7 @@ static int push_dl_task(struct rq *rq)
> > > >  		 * then possible that next_task has migrated.
> > > >  		 */
> > > >  		task = pick_next_pushable_dl_task(rq);
> > > > -		if (task_cpu(next_task) == rq->cpu && task == next_task) {
> > > > +		if (task == next_task) {  
> > > 
> > > Seems a sensible optimization to me. Actually, we are doing the same for
> > > rt.c; Steve, Peter, do you think we should optimize that as well?
> > > 
> > 
> > Are we doing the same for push_rt_task()? I don't see it, and I don't
> > see it in tip/sched/core either. What I have is:
> > 
> >   if (task_cpu(next_task) == rq->cpu && task == next_task) {
> 
> Sorry, bad wording on my side. I meant the are currently checking the
> same conditions both for DL and for RT, and we should probably optimize
> RT as well if we are going to take this patch.
> 
> > 
> > But that said, I believe this patch is correct, and we should change
> > rt.c as well.
> > 
> 
> That's what I meant. :)
> 
> > 
> >   task = pick_next_pushable_dl_task(rq);
> > 
> > Which has:
> > 
> >   BUG_ON(rq->cpu != task_cpu(task))
> > 
> > when it returns a task other than NULL. Which means that task_cpu(task)
> > must be rq->cpu. Then if task == next_task, then task_cpu(next_task)
> > must be rq->cpu as well.
> 
> Right.
> 
> > 
> > Reviewed-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
> > 
> 
> You can also add mine
> 
> Reviewed-by: Juri Lelli <juri.lelli@arm.com>

Juri and steven, thank you very much for reviewing it.

I'm not sure and familiar with... Should I add your 'reviewed by' into
my patches by myself?

> 
> > Mind fixing rt.c if it hasn't been fixed already.
> > 
> > -- Steve

  parent reply	other threads:[~2017-02-16  2:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-15  5:11 [PATCH] sched/deadline: Remove unnecessary condition in push_dl_task() Byungchul Park
2017-02-15  5:22 ` Byungchul Park
2017-02-15 10:47 ` Juri Lelli
2017-02-15 11:37   ` Peter Zijlstra
2017-02-15 14:25   ` Steven Rostedt
2017-02-15 14:45     ` Juri Lelli
2017-02-15 14:55       ` Steven Rostedt
2017-02-16  2:17       ` Byungchul Park [this message]
2017-02-16  2:31         ` Steven Rostedt
2017-02-16  2:33           ` Steven Rostedt
2017-02-16  2:41             ` Byungchul Park

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=20170216021758.GS16086@X58A-UD3R \
    --to=byungchul.park@lge.com \
    --cc=juri.lelli@arm.com \
    --cc=juri.lelli@gmail.com \
    --cc=kernel-team@lge.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.abeni@santannapisa.it \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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