From: "Nicolas Castagné" <nicolas.castagne@imag.fr>
To: linux-kernel@vger.kernel.org
Subject: a few question on threads affinity and CPU shielding.
Date: Mon, 1 Dec 2003 18:43:16 +0100 [thread overview]
Message-ID: <D7F95611-2425-11D8-9C79-000393C76CA6@imag.fr> (raw)
Hi all,
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 ?
Especially, with the 2.6 release :
- is it possible to control the cpu affinity of threads (as for
processes) ?
- is there also a patch to shield cpu against the scheduler ?
- is there also a patch to shield cpu against all interruptions
(especially hard clock interrups) ?
We here are (very) used to SGI IRIX real time facilities, but also very
new to linux.
We plan on porting our hard-real-time applications for multisensorial
simulation on linux. These questions are very important to us.
Thx a lot in advance,
and please believe I am VERY sorry if this is not the correct list for
my questions, and if I disturbed serious work ;-).
If so, please let me know !
Nicolas
------------------------------------------------------------------------
--------------------------
Dr Nicolas CASTAGNE
Researcher, IR de l'ACROE / ICA,
Association pour la Création et la Recherche
sur les Outils d'Expression
Laboratoire Informatique et Création Artistique
INPG,
46 av. F. Viallet, 38000 Grenoble, France.
pro : (33) 4 76 57 46 60
fax : (33) 4 76 57 48 89
------------------------------------------------------------------------
--------------------------
next reply other threads:[~2003-12-01 17:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-01 17:43 Nicolas Castagné [this message]
2003-12-01 13:49 ` a few question on threads affinity and CPU shielding Tim Hockin
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:
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=D7F95611-2425-11D8-9C79-000393C76CA6@imag.fr \
--to=nicolas.castagne@imag.fr \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).