From: Jon Masters <jonmasters@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
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 22:49:13 +0100 [thread overview]
Message-ID: <35fb2e59041024144970522110@mail.gmail.com> (raw)
In-Reply-To: <20041024212359.GA7328@elte.hu>
On Sun, 24 Oct 2004 23:23:59 +0200, Ingo Molnar <mingo@elte.hu> wrote:
> 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.
I saw the posts. I should go check that out myself for interest's sake
- thanks for the info. Scheduling domains is something I haven't
looked in to in much detail yet as they're not something which usually
concern me greatly.
Jon.
next prev parent reply other threads:[~2004-10-24 21:55 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
2004-10-24 21:49 ` Jon Masters [this message]
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=35fb2e59041024144970522110@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=jonathan@jonmasters.org \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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.