From: Ingo Molnar <mingo@elte.hu>
To: Mitchell Erblich <erblichs@earthlink.net>
Cc: Mike Galbraith <efault@gmx.de>,
linux-kernel@vger.kernel.org, dmitry.adamushko@gmail.com
Subject: Re: QUESTION: RT & SCHED & fork: ?MISSING EQUIV of task_new_fairfor RT tasks.
Date: Fri, 24 Aug 2007 11:51:02 +0200 [thread overview]
Message-ID: <20070824095102.GA3615@elte.hu> (raw)
In-Reply-To: <000501c7df67$a644c9e0$6501a8c0@earthlink.net>
* Mitchell Erblich <erblichs@earthlink.net> wrote:
> Mike Galbraith wrote:
> >
> > On Tue, 2007-08-14 at 12:28 -0700, Mitchell Erblich wrote:
> > > Group, Ingo Molnar, etc,
> > >
> > > Why does the rt sched_class contain fewer elements than fair?
> > > missing is the RT for .task_new.
> >
> > No class specific initialization needs to be done for RT tasks.
> >
> > -Mike
>
>
> Mike, et al,
>
> one time: I was told that this group likes bottom posts.
( Mike did not top-post, so why this comment? )
> The logic of class independent code calling class scheduling
> dependent code, assumes that all functions are in ALL the class
> dependent sections.
>
> Minimally, if I agree with your above statement, I would assume
> that the function should still exist as a null type function.
> However, in reality, alot of RT class specific init is done. Just
> currently none of it is done in this non-existant function.
your original claim and these additional claims are both incorrect. What
Mike said is true: there is nothing "missing", RT class tasks do not
need any extra setup over what they already receive from the generic
function. A NULL pointer for sched_class->task_new means: "do default
setup, no class-specific setup needed". If you disagree with what we say
then please send a fix-patch or quote the specific code that is missing
something in your opinion.
Ingo
prev parent reply other threads:[~2007-08-24 9:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-15 18:10 QUESTION: RT & SCHED & fork: ?MISSING EQUIV of task_new_fairfor RT tasks Mitchell Erblich
2007-08-16 6:44 ` Mike Galbraith
2007-08-24 9:51 ` Ingo Molnar [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=20070824095102.GA3615@elte.hu \
--to=mingo@elte.hu \
--cc=dmitry.adamushko@gmail.com \
--cc=efault@gmx.de \
--cc=erblichs@earthlink.net \
--cc=linux-kernel@vger.kernel.org \
/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