archive mirror
 help / color / mirror / Atom feed
From: Tim Hockin <>
To: "Nicolas Castagné" <>
Subject: Re: a few question on threads affinity and CPU shielding.
Date: Mon, 1 Dec 2003 05:49:19 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Mon, Dec 01, 2003 at 06:43:16PM +0100, Nicolas Castagné wrote:
> I  was very pleased that some patches for controlling CPU affinities  
> were merged in the 2.5 (and 2.6) releases of the kernel.
> Where may I find precisions on the patches that are now included ?

> - is there also a patch to shield cpu against the scheduler ?

I have a patch around that does this (against RedHat's backported O(1)).
Forward porting it should be no more difficult that creating it in the first
place :)  I was waiting until after 2.6.x was more stable to offer it.

> - is there also a patch to shield cpu against all interruptions  
> (especially hard clock interrups) ?

This could be added to my patch.

What my patch added was a sched_setprocstate() syscall, which lets you set a
CPU's run state.  Currently I support:

ENABLED - run any task
RESTRICTED - run only tasks with (cpus_allowed == 1 << cpu)
ISOLATED - run only tasks with
	(cpus_allowed == 1 << cpu && cpus_allowed_mask == 1 << cpu)


  reply	other threads:[~2003-12-01 17:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-01 17:43 a few question on threads affinity and CPU shielding Nicolas Castagné
2003-12-01 13:49 ` Tim Hockin [this message]
2003-12-02 18:57 ` Dimitri Sivanich

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).