From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Ken.Wakita@mail.is.titech.ac.jp (Ken Wakita)
Cc: caml-list@inria.fr
Subject: Re: Thread library for ocamlopt?
Date: Thu, 28 Aug 1997 13:30:56 +0200 (MET DST) [thread overview]
Message-ID: <199708281130.NAA25330@pauillac.inria.fr> (raw)
In-Reply-To: <199708270907.SAA11454@nsb.is.titech.ac.jp> from Ken Wakita at "Aug 27, 97 06:07:09 pm"
> Is there a plan to include the Thread module in the native compiler
> framework? Or is there a work done with native concurrent ocaml?
The existing thread library works by context-switching at the level of
the bytecode interpreter. This makes it highly portable to most Unix
systems, but of course the technique does not extend to the
native-code compiler.
To support native code, the thread library must be built on top of
"real" OS threads, e.g. Posix 1003.1c threads or Win32 threads.
We have such an implementation of Caml threads for Win32 (bytecode
only). Some work is in progress to extend it to Posix threads and to
the native-code compiler. The two main drawbacks are:
* Available only on Unix systems that provide fully conformant Posix
1003.1c threads, e.g. Solaris 2.5, Digital Unix 4.0, or Linux with
LinuxThreads, but not HPUX, SunOS, nor earlier versions of Digital
Unix, for instance.
* Preemption of long-running threads can only occur at allocation
points (for reasons relevant to both the garbage collector and the
handling of signals in ocamlopt), which can result in a relatively
rough scheduling for compute-bound threads.
- Xavier Leroy
next prev parent reply other threads:[~1997-08-29 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-27 9:07 Ken Wakita
1997-08-28 11:30 ` Xavier Leroy [this message]
1997-08-29 18:01 ` Thorsten Ohl
1997-09-01 15:24 ` 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=199708281130.NAA25330@pauillac.inria.fr \
--to=xavier.leroy@inria.fr \
--cc=Ken.Wakita@mail.is.titech.ac.jp \
--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