From: Christophe Raffalli <raffalli@univ-savoie.fr>
To: james woodyatt <jhw@wetware.com>, caml-list@inria.fr
Subject: Re: [Caml-list] Threads
Date: Sat, 11 Jun 2005 23:03:10 +0200 [thread overview]
Message-ID: <42AB518E.8070106@univ-savoie.fr> (raw)
In-Reply-To: <55fb30900b308b38d2724c53008f7c91@wetware.com>
james woodyatt a écrit :
> On 11 Jun 2005, at 00:46, Christophe Raffalli wrote:
>
>>
>> No there is a global mutex for caml thread. The only thing you can do
>> is have one Caml thread and many C threads running in the same time.
>>
>> This starts really to be an annoying limitation of the Caml runtime
>> now that you can have easily two dual core processors in one machine
>> ... (means four CPU)
>
>
> Not for me it isn't-- I gave up cooperative scheduling with Mac OS 9.
>
> Now, when I want concurrent, preëmptive multiprocessing, I call
> fork(2) [and often exec(2)], like Nature intended. I don't know why
> you folks on Win32 platforms continue to put up with such abominable
> support for POSIX interfaces.
>
>
Does not depend what you use (Posix, win32 threads etc ...), OCaml does
not support two threads accessing the memory at the same time.
next prev parent reply other threads:[~2005-06-11 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 17:56 Threads Jonathan Bryant
2005-06-11 7:46 ` [Caml-list] Threads Christophe Raffalli
2005-06-11 14:02 ` james woodyatt
2005-06-11 21:03 ` Christophe Raffalli [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-08 17:33 threads ygrek
2009-09-08 23:20 ` [Caml-list] threads Philippe Wang
2009-09-10 18:17 ` ygrek
2002-03-20 2:59 Francois Rouaix
2002-03-20 8:11 ` Remi VANICAT
2002-03-20 10:54 ` Sylvain LE GALL
2002-03-22 14:55 ` Xavier Leroy
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=42AB518E.8070106@univ-savoie.fr \
--to=raffalli@univ-savoie.fr \
--cc=caml-list@inria.fr \
--cc=jhw@wetware.com \
/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).