From: Donald Wakefield <don.wakefield@gmail.com>
To: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Thread and kernel 2.6 pb still there in CVS
Date: Fri, 9 Jul 2004 16:21:52 -0700 [thread overview]
Message-ID: <cfc41b1c040709162130ba0875@mail.gmail.com> (raw)
In-Reply-To: <20040628150805.GC7353@yquem.inria.fr>
On Mon, 28 Jun 2004 17:08:05 +0200, Xavier Leroy <xavier.leroy@inria.fr> wrote:
>
> The 2.6 Linux kernels changed the behavior of sched_yield() in a way
> that causes the unfairness you observed. Other threaded applications
> are affected, including Open Office (!). My belief is that it's
> really a bug in 2.6 kernels and that the new behavior of sched_yield(),
> while technically conformant to the POSIX specs, lowers the quality of
> implementation quite a lot.
>
> (I seem to remember from my LinuxThreads development days that this
> isn't the first time the kernel developers broke sched_yield(), then
> realized their error.)
I know this comes a bit late in this 'thread', but there's been
discussion on Slashdot on a new scheduler framework called Bossa. I
posted a quote from Xavier's discussion of sched_yield, and another
poster replied. In brief:
"...OpenOffice.org and Ocaml have to wait too long for their next CPU
quantum, but that's because they are CPU bound tasks and it's their
own fault.
"The bug was in past versions of Linux where, although it was
pre-emptive, sched_yield was allowed some power - it should have been
ignored in user-space and the scheduler decided what gets CPU and
when. Depending on that bug is also a bug and the mis-users deserve
everything they get."
The full reply can be read at:
<http://slashdot.org/comments.pl?sid=113880&cid=9655540>
--
Don Wakefield
don.wakefield@gmail.com
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-07-09 23:22 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 22:41 [Caml-list] Why must types be always defined at the top level? Richard Jones
2004-06-22 22:53 ` Markus Mottl
2004-06-22 23:32 ` skaller
2004-06-23 12:01 ` Andreas Rossberg
2004-06-23 14:45 ` skaller
2004-06-23 16:28 ` Andreas Rossberg
2004-06-23 20:21 ` skaller
2004-06-23 20:52 ` skaller
2004-06-24 14:27 ` John Hughes
2004-06-24 16:47 ` Andreas Rossberg
2004-06-24 17:30 ` Markus Mottl
2004-06-24 17:45 ` Xavier Leroy
2004-06-24 19:46 ` John Hughes
2004-06-24 19:56 ` David Brown
2004-06-24 19:57 ` William D. Neumann
2004-06-24 20:13 ` Olivier Andrieu
2004-06-24 23:26 ` Brian Hurt
2004-06-25 10:20 ` skaller
2004-06-25 11:07 ` Basile Starynkevitch [local]
2004-06-25 12:30 ` skaller
2004-06-25 14:38 ` [Caml-list] Thread and kernel 2.6 pb still there in CVS Christophe Raffalli
2004-06-25 16:08 ` [Caml-list] " Marco Maggesi
2004-06-25 16:32 ` Markus Mottl
2004-06-28 15:08 ` [Caml-list] " Xavier Leroy
2004-06-28 18:50 ` Benjamin Geer
2004-06-29 2:26 ` Christophe Raffalli
[not found] ` <7AFB5F64-C944-11D8-975C-00039310CAE8@inria.fr>
[not found] ` <40E11621.3050709@univ-savoie.fr>
2004-07-05 15:14 ` Christophe Raffalli
2004-07-05 16:34 ` Xavier Leroy
2004-07-06 9:33 ` Alex Baretta
2004-07-08 13:51 ` Christophe Raffalli
2004-07-08 15:03 ` Xavier Leroy
2004-07-09 23:21 ` Donald Wakefield [this message]
2004-07-10 10:56 ` Damien Doligez
2004-06-24 23:23 ` [Caml-list] Why must types be always defined at the top level? Brian Hurt
[not found] ` <Pine.LNX.4.44.0406241813370.4202-100000@localhost.localdom ain>
2004-06-26 23:08 ` Dave Berry
2004-06-25 1:59 ` Yaron Minsky
2004-06-24 23:08 ` Brian Hurt
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=cfc41b1c040709162130ba0875@mail.gmail.com \
--to=don.wakefield@gmail.com \
--cc=caml-list@inria.fr \
/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