From: Peter Zijlstra <peterz@infradead.org>
To: Primiano Tucci <p.tucci@gmail.com>
Cc: rostedt@goodmis.org, linux-kernel@vger.kernel.org,
tglx <tglx@linutronix.de>, Bjoern Brandenburg <bbb@email.unc.edu>
Subject: Re: Considerations on sched APIs under RT patch
Date: Thu, 22 Apr 2010 18:28:06 +0200 [thread overview]
Message-ID: <1271953686.1776.372.camel@laptop> (raw)
In-Reply-To: <k2gc5b2c05b1004220840z59f9417fy723a36a6fe9924dc@mail.gmail.com>
On Thu, 2010-04-22 at 17:40 +0200, Primiano Tucci wrote:
> > Its a well studied
> > algorithm and even available in commercial SMP operating systems
>
> Can you cite me a commercial SMP system that supports
> multicore/multiprocessor G-EDF?
From: http://www.cs.unc.edu/~anderson/papers/rtlws09.pdf
"Regarding the frequently voiced objections to G-
EDF’s viability in a “real” system, it should be noted that
xnu, the kernel underlying Apple’s multimedia-friendly
OS X, has been relying on G-EDF to support real-time
applications on multiprocessors for several years [5]."
"[5] Apple Inc. xnu source code.
http://opensource.apple.com/source/xnu/."
> > Implementing this as userspace/middleware seems daft. But if your
> > controlling process has a global affinity mask and runs as the highest
> > available userspace process priority its still all valid.
>
> It is how it is implemented now, and how it works under VXWorks!
But that does not, and can not, provide proper isolation and bandwidth
guarantees since there could be runnable tasks outside the scope of the
middleware.
next prev parent reply other threads:[~2010-04-22 16:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 20:48 Considerations on sched APIs under RT patch Primiano Tucci
2010-04-20 9:20 ` Peter Zijlstra
2010-04-20 21:56 ` Primiano Tucci
2010-04-20 23:00 ` Steven Rostedt
2010-04-21 5:16 ` Primiano Tucci
2010-04-21 8:49 ` Peter Zijlstra
2010-04-21 12:46 ` Steven Rostedt
2010-04-21 19:24 ` Primiano Tucci
2010-04-21 19:57 ` Peter Zijlstra
2010-04-21 20:38 ` Primiano Tucci
2010-04-21 20:58 ` Peter Zijlstra
2010-04-22 13:20 ` Steven Rostedt
2010-04-22 13:50 ` Primiano Tucci
2010-04-22 13:57 ` Peter Zijlstra
2010-04-22 15:40 ` Primiano Tucci
2010-04-22 16:28 ` Peter Zijlstra [this message]
2010-04-22 17:48 ` Bjoern Brandenburg
2010-04-22 19:33 ` Primiano Tucci
2010-04-21 12:56 ` Peter Zijlstra
2010-04-27 13:18 ` Thomas Gleixner
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=1271953686.1776.372.camel@laptop \
--to=peterz@infradead.org \
--cc=bbb@email.unc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=p.tucci@gmail.com \
--cc=rostedt@goodmis.org \
--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