From: Ingo Molnar <mingo@elte.hu>
To: Loic Domaigne <loic-dev@gmx.net>
Cc: Nick Piggin <piggin@cyberone.com.au>,
nptl@bullopensource.org, Linux-Kernel@Vger.Kernel.ORG
Subject: Re: OSDL Bug 3770
Date: Tue, 21 Dec 2004 14:32:13 +0100 [thread overview]
Message-ID: <20041221133213.GA16238@elte.hu> (raw)
In-Reply-To: <25289.1103630797@www66.gmx.net>
* Loic Domaigne <loic-dev@gmx.net> wrote:
> > Yes, it does support hard CPU binding - sched_setaffinity
>
> Yes, I believe that /sched_setaffinity()/ offers a practical solution
> to the problem we are faced.
that's the short-term workaround. Another model for CPU-bound RT tasks
is the use of isolcpus. (see Documentation/kernel-parameters.txt)
but that's the thinking behind current RT scheduling: no global sorting
of priorities is done on SMP, but if you know the priorities and the
workload in advance you can manually bind them to specific CPUs.
> But I am eager to try the RT-patchset of Ingo.
this is obviously more experimental stuff, and feedback is welcome. It
is the current 'playground' for RT related scheduling features.
Ingo
next prev parent reply other threads:[~2004-12-21 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-20 17:02 Re: OSDL Bug 3770 Loic Domaigne
2004-12-21 10:09 ` Ingo Molnar
2004-12-21 10:20 ` Loic Domaigne
2004-12-21 10:22 ` [nptl] " Sebastien Decugis
2004-12-24 15:00 ` Sebastien Decugis
2004-12-21 11:09 ` Nick Piggin
2004-12-21 12:06 ` Loic Domaigne
2004-12-21 13:32 ` Ingo Molnar [this message]
[not found] <1102071900.14792.81.camel@decugiss.frec.bull.fr>
[not found] ` <41B6368F.9060704@cyberone.com.au>
[not found] ` <1102495648.3613.39.camel@decugiss.frec.bull.fr>
[not found] ` <41B6C2D4.5040705@cyberone.com.au>
[not found] ` <1102497754.3644.1.camel@decugiss.frec.bull.fr>
[not found] ` <41B6D544.1010106@cyberone.com.au>
[not found] ` <1102501896.3644.5.camel@decugiss.frec.bull.fr>
[not found] ` <41B6D824.80804@cyberone.com.au>
[not found] ` <41B6DA44.4020100@cyberone.com.au>
[not found] ` <1102502987.3644.7.camel@decugiss.frec.bull.fr>
[not found] ` <41B6DEC1.9050506@cyberone.com.au>
[not found] ` <1102523077.3644.42.camel@decugiss.frec.bull.fr>
[not found] ` <41B8115C.30509@cyberone.com.au>
[not found] ` <41B82435.7020802@cyberone.com.au>
[not found] ` <1102590314.3644.107.camel@decugiss.frec.bull.fr>
[not found] ` <41C3F4BB.2050102@gmx.net>
2004-12-18 9:43 ` Nick Piggin
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=20041221133213.GA16238@elte.hu \
--to=mingo@elte.hu \
--cc=Linux-Kernel@Vger.Kernel.ORG \
--cc=loic-dev@gmx.net \
--cc=nptl@bullopensource.org \
--cc=piggin@cyberone.com.au \
/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