From: tip-bot for Hillf Danton <dhillf@gmail.com>
To: linux-tip-commits@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, hpa@zytor.com, mingo@redhat.com,
a.p.zijlstra@chello.nl, dhillf@gmail.com, rostedt@goodmis.org,
tglx@linutronix.de, yong.zhang0@gmail.com, mingo@elte.hu
Subject: [tip:sched/core] sched: Remove noop in next_prio()
Date: Sun, 14 Aug 2011 15:59:36 GMT [thread overview]
Message-ID: <tip-67d955383ab2ef8866c494c14156a4f3d29e441c@git.kernel.org> (raw)
In-Reply-To: <BANLkTimxmWiof9s5AvS3v_0X+sMiE=0x5g@mail.gmail.com>
Commit-ID: 67d955383ab2ef8866c494c14156a4f3d29e441c
Gitweb: http://git.kernel.org/tip/67d955383ab2ef8866c494c14156a4f3d29e441c
Author: Hillf Danton <dhillf@gmail.com>
AuthorDate: Thu, 16 Jun 2011 21:55:18 -0400
Committer: Ingo Molnar <mingo@elte.hu>
CommitDate: Sun, 14 Aug 2011 12:00:45 +0200
sched: Remove noop in next_prio()
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 tasks are returned by the
function.
Reviewed-by: Yong Zhang <yong.zhang0@gmail.com>
Signed-off-by: Hillf Danton <dhillf@gmail.com>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
Link: http://lkml.kernel.org/r/BANLkTimxmWiof9s5AvS3v_0X+sMiE=0x5g@mail.gmail.com
Signed-off-by: Ingo Molnar <mingo@elte.hu>
---
kernel/sched_rt.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/kernel/sched_rt.c b/kernel/sched_rt.c
index 97540f0..e2698c0 100644
--- a/kernel/sched_rt.c
+++ b/kernel/sched_rt.c
@@ -704,7 +704,7 @@ static inline int next_prio(struct rq *rq)
{
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;
prev parent reply other threads:[~2011-08-14 15:59 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
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-bot for Hillf Danton [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=tip-67d955383ab2ef8866c494c14156a4f3d29e441c@git.kernel.org \
--to=dhillf@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--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