From: Christophe Raffalli <christophe.raffalli@univ-savoie.fr>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Thread and kernel 2.6 pb still there in CVS
Date: Thu, 08 Jul 2004 09:51:00 -0400 [thread overview]
Message-ID: <40ED5144.8050903@univ-savoie.fr> (raw)
In-Reply-To: <40EA71ED.9040005@baretta.com>
I did again some testing, with a Caml program with 2 thread, one doing
only float computation for a long time with no allocation. The nanosleep
suggestion seems much better than the actual version doing nothing:
This gives the following code in systhreads/posix.c:
/* Allow re-scheduling */
value caml_thread_yield(value unit) /* ML */
{
struct timespec timer = { 0, 1 };
enter_blocking_section();
nanosleep (&timer, NULL);
/* sched_yield();*/
leave_blocking_section();
return Val_unit;
}
--
Christophe Raffalli
Université de Savoie
Batiment Le Chablais, bureau 21
73376 Le Bourget-du-Lac Cedex
tél: (33) 4 79 75 81 03
fax: (33) 4 79 75 87 42
mail: Christophe.Raffalli@univ-savoie.fr
www: http://www.lama.univ-savoie.fr/~RAFFALLI
---------------------------------------------
IMPORTANT: this mail is signed using PGP/MIME
At least Enigmail/Mozilla, mutt or evolution
can check this signature
---------------------------------------------
-------------------
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-08 7:51 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 [this message]
2004-07-08 15:03 ` Xavier Leroy
2004-07-09 23:21 ` Donald Wakefield
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=40ED5144.8050903@univ-savoie.fr \
--to=christophe.raffalli@univ-savoie.fr \
--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