[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1356094312.5896.97.camel@gandalf.local.home>
Date: Fri, 21 Dec 2012 07:51:52 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Kirill Tkhai <tkhai@...dex.ru>
Cc: Thomas Gleixner <tglx@...utronix.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
linux-rt-users <linux-rt-users@...r.kernel.org>
Subject: Re: [PATCH] sched/rt: Move cpu rq properties from "struct rt_rq" to
"struct rq"
On Fri, 2012-12-21 at 10:35 +0400, Kirill Tkhai wrote:
>
>
> entity_1->my_q_1
> /
> /
> rq->rt -entity_2->my_q_2
> \
> \
> entity_n->my_q_n
>
>
> I say about child rt_rqs (my_q_1....my_q_n). They don't have rt_nr_total, rt_nr_migratory, overloaded and pushable_tasks.
> The only use of overloaded, for example, is "rq->rt.overloaded". The same with other variables.
You're missing the point. rt_rq is not just for entities, it's the
encapsulation of the rt class.
Now if you want to encapsulate the rt sched group, then you could add a
new struct and put that into the rt_rq struct and use that for all the
group functions. But please don't just cludder the rq struct with rt
specific data. The rt_rq was created as a container for the rt class.
-- Steve
--
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