[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <tip-1437f5bca3c2d162f058cba37dfbeb20f619040d@git.kernel.org>
Date: Tue, 26 Apr 2011 12:58:01 GMT
From: tip-bot for Hillf Danton <dhillf@...il.com>
To: linux-tip-commits@...r.kernel.org
Cc: linux-kernel@...r.kernel.org, hpa@...or.com, mingo@...hat.com,
dhillf@...il.com, a.p.zijlstra@...llo.nl, yong.zhang0@...il.com,
tglx@...utronix.de, mingo@...e.hu
Subject: [tip:sched/core] sched: Remove noop in alloc_rt_sched_group()
Commit-ID: 1437f5bca3c2d162f058cba37dfbeb20f619040d
Gitweb: http://git.kernel.org/tip/1437f5bca3c2d162f058cba37dfbeb20f619040d
Author: Hillf Danton <dhillf@...il.com>
AuthorDate: Sat, 23 Apr 2011 21:29:05 +0800
Committer: Ingo Molnar <mingo@...e.hu>
CommitDate: Tue, 26 Apr 2011 13:34:08 +0200
sched: Remove noop in alloc_rt_sched_group()
The rq varible, though computed for each possible cpu, has nothing to
do in the function, so it can be removed.
This also eliminates a build warning.
Signed-off-by: Hillf Danton <dhillf@...il.com>
Reviewed-by: Yong Zhang <yong.zhang0@...il.com>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Link: http://lkml.kernel.org/r/BANLkTin-FfQfqW5ym1iuEmrk8s777Y1LAg@mail.gmail.com
Signed-off-by: Ingo Molnar <mingo@...e.hu>
---
kernel/sched.c | 3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/kernel/sched.c b/kernel/sched.c
index 9cde2dd..f11a2a5 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -8226,7 +8226,6 @@ int alloc_rt_sched_group(struct task_group *tg, struct task_group *parent)
{
struct rt_rq *rt_rq;
struct sched_rt_entity *rt_se;
- struct rq *rq;
int i;
tg->rt_rq = kzalloc(sizeof(rt_rq) * nr_cpu_ids, GFP_KERNEL);
@@ -8240,8 +8239,6 @@ int alloc_rt_sched_group(struct task_group *tg, struct task_group *parent)
ktime_to_ns(def_rt_bandwidth.rt_period), 0);
for_each_possible_cpu(i) {
- rq = cpu_rq(i);
-
rt_rq = kzalloc_node(sizeof(struct rt_rq),
GFP_KERNEL, cpu_to_node(i));
if (!rt_rq)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists