From: Ingo Molnar <mingo@elte.hu>
To: Bill Huey <billh@gnuppy.monkey.org>
Cc: Darren Hart <darren@dvhart.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"Stultz, John" <johnstul@us.ibm.com>,
Peter Williams <pwil3058@bigpond.net.au>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: RT task scheduling
Date: Fri, 7 Apr 2006 11:19:46 +0200 [thread overview]
Message-ID: <20060407091946.GA28421@elte.hu> (raw)
In-Reply-To: <20060407083931.GA11393@gnuppy.monkey.org>
* Bill Huey <billh@gnuppy.monkey.org> wrote:
> On Fri, Apr 07, 2006 at 09:11:25AM +0200, Ingo Molnar wrote:
> > * Bill Huey <billh@gnuppy.monkey.org> wrote:
> >
> > > On Thu, Apr 06, 2006 at 09:37:53AM +0200, Ingo Molnar wrote:
> > > > do "global" decisions for what RT tasks to run on which CPU. To put even
> > > > less overhead on the mainstream kernel, i plan to introduce a new
> > > > SCHED_FIFO_GLOBAL scheduling policy to trigger this behavior. [it doesnt
> > > > make much sense to extend SCHED_RR in that direction.]
> > >
> > > You should consider for a moment to allow for the binding of a thread
> > > to a CPU to determine the behavior of a SCHED_FIFO class task instead
> > > of creating a new run category. [...]
> >
> > That is already possible and has been possible for years.
>
> I know that this is already the case. What I'm saying is that the
> creation of new globally scheduled run case isn't necessarly if you
> have a robust thread to CPU binding mechanism, [...]
-ENOPARSE. CPU binding brings with itself obvious disadvantages that
some applications are not ready to pay. CPU binding restricts the
scheduler from achieving best resource utilization. That may be fine for
some applications, but is not good enough for a good number of
applications. So in no way can any 'CPU binding mechanism' (which
already exists in multiple forms) replace the need and desire for a
globally scheduled class of RT tasks.
> [...] the key here is "robust". [...]
-ENOPARSE. CPU binding is CPU binding. Could you outline an example of a
"non-robust" CPU binding solution?
Ingo
next prev parent reply other threads:[~2006-04-07 9:22 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 3:25 RT task scheduling Darren Hart
2006-04-06 4:19 ` Peter Williams
2006-04-06 17:24 ` Darren Hart
2006-04-06 23:02 ` Peter Williams
2006-04-06 7:37 ` Ingo Molnar
2006-04-06 14:55 ` Darren Hart
2006-04-06 18:16 ` Darren Hart
2006-04-06 22:35 ` Darren Hart
2006-04-07 22:58 ` Vernon Mauery
2006-04-06 23:06 ` Peter Williams
2006-04-07 3:07 ` Bill Huey
2006-04-07 7:11 ` Ingo Molnar
2006-04-07 8:39 ` Bill Huey
2006-04-07 9:11 ` Bill Huey
2006-04-07 9:19 ` Ingo Molnar [this message]
2006-04-07 10:39 ` Bill Huey
2006-04-07 10:51 ` Ingo Molnar
2006-04-07 11:14 ` Bill Huey
2006-04-07 11:29 ` Ingo Molnar
2006-04-07 22:18 ` Bill Huey
2006-04-07 14:56 ` Darren Hart
2006-04-07 21:06 ` Bill Huey
2006-04-07 22:37 ` Darren Hart
2006-04-07 23:36 ` Bill Huey
2006-04-08 3:01 ` Steven Rostedt
2006-04-08 4:28 ` Vernon Mauery
2006-04-08 4:45 ` Steven Rostedt
2006-04-08 7:16 ` Ingo Molnar
2006-04-08 7:25 ` Ingo Molnar
2006-04-08 7:54 ` Bill Huey
2006-04-08 8:03 ` Ingo Molnar
2006-04-08 10:02 ` Bill Huey
2006-04-08 0:11 ` Peter Williams
2006-04-07 9:23 ` Bill Huey
2006-04-09 13:16 ` Ingo Molnar
2006-04-09 17:25 ` Darren Hart
2006-04-09 18:31 ` Ingo Molnar
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=20060407091946.GA28421@elte.hu \
--to=mingo@elte.hu \
--cc=billh@gnuppy.monkey.org \
--cc=darren@dvhart.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=pwil3058@bigpond.net.au \
--cc=suresh.b.siddha@intel.com \
--cc=tglx@linutronix.de \
/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).