From: Steven Rostedt <rostedt@goodmis.org>
To: Kirill Tkhai <tkhai@yandex.ru>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH] sched/rt: Move cpu rq properties from "struct rt_rq" to "struct rq"
Date: Fri, 21 Dec 2012 07:51:52 -0500 [thread overview]
Message-ID: <1356094312.5896.97.camel@gandalf.local.home> (raw)
In-Reply-To: <545781356071709@web16g.yandex.ru>
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
next prev parent reply other threads:[~2012-12-21 12:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-18 19:12 [PATCH] sched/rt: Move cpu rq properties from "struct rt_rq" to "struct rq" Kirill Tkhai
2012-12-20 17:53 ` Thomas Gleixner
2012-12-20 22:16 ` Kirill Tkhai
2012-12-20 23:07 ` Steven Rostedt
2012-12-21 6:35 ` Kirill Tkhai
2012-12-21 12:51 ` Steven Rostedt [this message]
2012-12-21 14:43 ` Steven Rostedt
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=1356094312.5896.97.camel@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tkhai@yandex.ru \
/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;
as well as URLs for NNTP newsgroup(s).