From: Sven Luther <luther@dpt-info.u-strasbg.fr>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: Blair Zajac <blair@orcaware.com>, caml-list@inria.fr
Subject: Re: [Caml-list] Why systhreads?
Date: Tue, 26 Nov 2002 10:29:24 +0100 [thread overview]
Message-ID: <20021126092924.GA5383@iliana> (raw)
In-Reply-To: <20021126100254.A19708@pauillac.inria.fr>
On Tue, Nov 26, 2002 at 10:02:54AM +0100, Xavier Leroy wrote:
> Blair Zajac wrote:
>
> > To summarize, for (2) system threads are required and and you can't
> > prevent blocking with user level threads easily or at all. For (3),
> > making the Ocaml system support SMP is "Too complex; too hard to
> > debug" and SMP boxes aren't all that popular.
> > Aren't these contradictory statements?
> >
> > For Ocaml to support a Ocaml program to have one thread to block on a
> > system call and to allow other threads to continue, doesn't this support
> > SMP? Does Ocaml support this?
>
> No to the first question. Yes to the second.
>
> By "supporting SMP", I mean having several threads executing Caml code
> in parallel, thus using the Caml runtime system in a concurrent fashion.
> This is the hard part.
>
> In the current implementation of systhreads, the Caml executor and
> runtime system is one big critical section: at most one thread can
> execute Caml code at a given time, but arbitrarily many other threads
> can be blocked on I/O (and thus isn't calling the Caml runtime system).
> Each thread leaves the critical section before calling a potentially
> blocking I/O operation, and re-enters it when the I/O completes.
In the case i have a multi-threaded lablgtk executable, having ine
thread managing the interface and the other running programs, that even
if i had a way of killing a thread (or setting a mutex or whatever to
signal it to stop), that if the running thread is looping, i will never
be able to execute the interface thread which will (trough a callback)
set the mutex to the stop option, because the running thread doesn't do
blocking IO ?
Mmm, checking the mutex is a blocking IO though, isn't it ?
keeping the GUI alive even if some other stuff is taking time or looping
forever is a nice application of threading support.
Friendly,
Sven Luther
-------------------
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:[~2002-11-26 9:29 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-23 9:08 Lauri Alanko
2002-11-24 7:36 ` Sven Luther
2002-11-24 17:41 ` Chris Hecker
2002-11-24 18:12 ` Basile STARYNKEVITCH
2002-11-24 21:10 ` Christopher Quinn
2002-11-24 17:14 ` Vitaly Lugovsky
2002-11-24 17:18 ` Lauri Alanko
2002-11-24 18:27 ` Dmitry Bely
2002-11-24 23:14 ` Vitaly Lugovsky
2002-11-27 14:33 ` Tim Freeman
2002-11-29 13:25 ` Vitaly Lugovsky
2002-11-25 10:01 ` Xavier Leroy
2002-11-25 14:20 ` Markus Mottl
2002-11-25 19:01 ` Blair Zajac
2002-11-25 21:06 ` james woodyatt
2002-11-25 22:20 ` Chris Hecker
2002-11-26 6:49 ` Sven Luther
2002-11-27 13:12 ` Damien Doligez
2002-11-27 18:04 ` Chris Hecker
2002-11-27 21:04 ` Gerd Stolpmann
2002-11-27 21:45 ` [Caml-list] Calling ocaml from external threads Quetzalcoatl Bradley
2002-11-26 9:02 ` [Caml-list] Why systhreads? Xavier Leroy
2002-11-26 9:29 ` Sven Luther [this message]
2002-11-26 9:34 ` Xavier Leroy
2002-11-26 9:39 ` Sven Luther
2002-11-26 18:42 ` Chris Hecker
2002-11-26 19:04 ` Dave Berry
2002-11-27 0:07 ` Lauri Alanko
2002-11-26 19:23 Gregory Morrisett
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=20021126092924.GA5383@iliana \
--to=luther@dpt-info.u-strasbg.fr \
--cc=blair@orcaware.com \
--cc=caml-list@inria.fr \
--cc=xavier.leroy@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