From: Ingo Molnar <mingo@elte.hu>
To: Jon Masters <jonathan@jonmasters.org>
Cc: paulmck@us.ibm.com, Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
karim@opersys.com
Subject: Re: [RFC][PATCH] Restricted hard realtime
Date: Sun, 24 Oct 2004 23:23:59 +0200 [thread overview]
Message-ID: <20041024212359.GA7328@elte.hu> (raw)
In-Reply-To: <417C19D5.7050802@jonmasters.org>
* Jon Masters <jonathan@jonmasters.org> wrote:
> I guess it would. But then we've just had a slew of RT implementations
> crawl out of the woodwork and wave at us over the past few weeks and
> there are three other major RT implementations which combine Linux
> with a Microkernel or other external support (RTLinux, RTAI, KURT,
> etc.). Perhaps it's worth working on one of the Linux patch projects
> (Monta/Ingo/etc.) rather than going all out to implement it all again.
also note that (as i mentioned it in an earlier reply to Paul) the
'CPU[s] isolated for hard-RT use' scheduler feature has already been
implemented by Dimitri Sivanich and was accepted and integrated into the
2.6.9 kernel a couple of weeks ago.
Isolated CPUs can be set up via the "isolcpus=" boot parameter, and can
be entered via the affinity syscall. The feature came with related fixes
to the scheduler and other kernel code to eliminate cross-effects
between domains. (such as the scheduler balancing code, or the swap
tick)
So this all is banging on open doors, this particular mode of hard-RT
scheduling is there and available in vanilla Linux. If anyone wants to
try it, just download 2.6.9 and use it.
Ingo
next prev parent reply other threads:[~2004-10-24 21:22 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-23 19:47 [RFC][PATCH] Restricted hard realtime Paul E. McKenney
2004-10-23 20:17 ` Ingo Molnar
2004-10-23 20:29 ` Paul E. McKenney
2004-10-24 18:18 ` Paul E. McKenney
2004-10-25 12:26 ` Dimitri Sivanich
2004-10-23 20:22 ` Thomas Gleixner
2004-10-23 21:24 ` Paul E. McKenney
2004-10-23 22:06 ` Jon Masters
2004-10-24 15:32 ` Paul E. McKenney
2004-10-24 21:08 ` Jon Masters
2004-10-24 21:23 ` Ingo Molnar [this message]
2004-10-24 21:49 ` Jon Masters
2004-10-24 21:52 ` Paul E. McKenney
2004-10-27 3:16 ` Karim Yaghmour
2004-10-27 4:29 ` Andrew Morton
2004-10-27 8:10 ` Ingo Molnar
2004-10-28 11:59 ` Karim Yaghmour
2004-10-28 13:16 ` Ingo Molnar
2004-10-28 11:54 ` Karim Yaghmour
2004-10-28 13:04 ` john cooper
2004-10-27 22:35 ` Bill Huey
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=20041024212359.GA7328@elte.hu \
--to=mingo@elte.hu \
--cc=jonathan@jonmasters.org \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.