public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Yong Zhang <yong.zhang0@gmail.com>
Cc: Hillf Danton <dhillf@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH] sched: remove noop in next_prio()
Date: Tue, 24 May 2011 13:53:34 +0200	[thread overview]
Message-ID: <1306238014.16375.0.camel@marge.simson.net> (raw)
In-Reply-To: <BANLkTikhvhptDG-eRZ9uD5wSm3RxTn1RFw@mail.gmail.com>

On Tue, 2011-05-24 at 16:17 +0800, Yong Zhang wrote:
> On Sat, May 21, 2011 at 10:19 PM, Hillf Danton <dhillf@gmail.com> wrote:
> > When computing the next priority for a given run-queue, the check for
> > RT priority of the task determined by the pick_next_highest_task_rt()
> > function could be removed, since only RT task is returned by the
> > function.
> >
> > Signed-off-by: Hillf Danton <dhillf@gmail.com>
> 
> Yup, it's true.

(could whack the else while there)

> Reviewed-by: Yong Zhang <yong.zhang0@gmail.com>
> 
> > ---
> >
> > --- a/kernel/sched_rt.c 2011-04-27 11:48:50.000000000 +0800
> > +++ b/kernel/sched_rt.c 2011-05-21 22:10:34.000000000 +0800
> > @@ -670,7 +670,7 @@ static inline int next_prio(struct rq *r
> >  {
> >        struct task_struct *next = pick_next_highest_task_rt(rq, rq->cpu);
> >
> > -       if (next && rt_prio(next->prio))
> > +       if (next)
> >                return next->prio;
> >        else
> >                return MAX_RT_PRIO;
> >
> 
> 
> 



  reply	other threads:[~2011-05-24 11:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-21 14:19 [PATCH] sched: remove noop in next_prio() Hillf Danton
2011-05-24  8:17 ` Yong Zhang
2011-05-24 11:53   ` Mike Galbraith [this message]
2011-05-24 14:20     ` Hillf Danton
2011-05-24 14:16       ` Jesper Juhl
2011-05-24 14:26         ` Hillf Danton
2011-05-24 13:09 ` Steven Rostedt
2011-08-14 15:59 ` [tip:sched/core] sched: Remove " tip-bot for Hillf Danton

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=1306238014.16375.0.camel@marge.simson.net \
    --to=efault@gmx.de \
    --cc=dhillf@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=yong.zhang0@gmail.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