From: "Loic Domaigne" <loic-dev@gmx.net>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: nptl@bullopensource.org, Linux-Kernel@Vger.Kernel.ORG, mingo@elte.hu
Subject: Re: OSDL Bug 3770
Date: Tue, 21 Dec 2004 13:06:37 +0100 (MET) [thread overview]
Message-ID: <25289.1103630797@www66.gmx.net> (raw)
In-Reply-To: 41C8047E.1030403@cyberone.com.au
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="us-ascii", Size: 1079 bytes --]
Hello Nick,
> >Does Linux tolerate hard CPU binding? By hard CPU binding, I mean
> >that the application tells the scheduler "I want to run there",
> >and the scheduler schedules the thread(s) "there" regardless if it
> >makes sense or not ( The decision is left to the application).
>
> 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.
But I am eager to try the RT-patchset of Ingo.
> [snip interesting dialogue]
>
> Thanks for your detailed comments, they were interesting.
... Glad to hear. You're welcome!
Cheers,
Loic.
--
--
// Sender address goes to /dev/null (!!)
// Use my 32/64 bits, ANSI C89, compliant email-address instead:
unsigned y[]=
{0,34432,26811,16721,41866,63119,61007,48155,26147,10986};
void x(z){putchar(z);}; unsigned t;
main(i){if(i<10){t=(y[i]*47560)%65521;x(t>>8);x(t&255);main(++i);}}
+++ Sparen Sie mit GMX DSL +++ http://www.gmx.net/de/go/dsl
AKTION für Wechsler: DSL-Tarife ab 3,99 EUR/Monat + Startguthaben
next prev parent reply other threads:[~2004-12-21 12:06 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 [this message]
2004-12-21 13:32 ` Ingo Molnar
[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=25289.1103630797@www66.gmx.net \
--to=loic-dev@gmx.net \
--cc=Linux-Kernel@Vger.Kernel.ORG \
--cc=mingo@elte.hu \
--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