All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "Paul E. McKenney" <paulmck@us.ibm.com>
Cc: linux-kernel@vger.kernel.org, karim@opersys.com,
	Dimitri Sivanich <sivanich@sgi.com>
Subject: Re: [RFC][PATCH] Restricted hard realtime
Date: Sat, 23 Oct 2004 22:17:24 +0200	[thread overview]
Message-ID: <20041023201724.GA23936@elte.hu> (raw)
In-Reply-To: <20041023194721.GB1268@us.ibm.com>


* Paul E. McKenney <paulmck@us.ibm.com> wrote:

> +	bool "Reserve a CPU for hard realtime processes"

this has been implemented in a clean way already: check out the
"isolcpus=" boot option & scheduler feature (implemented by Dimitri
Sivanich) which isolates a set of CPUs via sched-domains for precisely
such purposes. The way to enter such a domain is via the affinity
syscall - and balancing will leave such domains isolated.

	ingo

  reply	other threads:[~2004-10-23 20:17 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 [this message]
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
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=20041023201724.GA23936@elte.hu \
    --to=mingo@elte.hu \
    --cc=karim@opersys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulmck@us.ibm.com \
    --cc=sivanich@sgi.com \
    /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.