From: Jan Kybic <kybic@fel.cvut.cz>
To: caml-list@inria.fr
Subject: Can coThreads be used for message passing architecture?
Date: Wed, 19 Sep 2007 12:58:29 +0200 [thread overview]
Message-ID: <87ps0e9b1m.fsf_-_@fel.cvut.cz> (raw)
In-Reply-To: <20070919201144.634be18a.mle+ocaml@mega-nerd.com> (Erik de Castro Lopo's message of "Wed, 19 Sep 2007 20:11:44 +1000")
>> I'd like to announce the first public release of coThreads, a concurrent
>> programming library for OCaml.
I have had only a quick look at the web page but I did not understand
whether and how can coThreads be used on a cluster of independent
computers (Beowulf-style) that are only connected by network (no
shared memory) for which I normally use MPI (message passing).
Is coThreads usable in such a scenario? What is the backend - does it
run on the top of PVM, MPI, or similar?
Thanks for clarification.
Jan
--
-------------------------------------------------------------------------
Jan Kybic <kybic@fel.cvut.cz> tel. +420 2 2435 5721
http://cmp.felk.cvut.cz/~kybic ICQ 200569450
next prev parent reply other threads:[~2007-09-19 10:57 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 16:31 [ANN] coThreads 0.10 Zheng Li
2007-09-17 16:48 ` Zheng Li
2007-09-17 17:39 ` [Caml-list] " skaller
2007-09-17 17:51 ` Zheng Li
2007-09-17 21:33 ` [Caml-list] " skaller
2007-09-17 22:37 ` Zheng Li
2007-09-17 23:26 ` [Caml-list] " skaller
2007-09-18 0:16 ` Zheng Li
2007-09-18 0:53 ` [Caml-list] " Erik de Castro Lopo
2007-09-18 1:25 ` Erik de Castro Lopo
2007-09-18 4:29 ` skaller
2007-09-19 10:11 ` Erik de Castro Lopo
2007-09-19 10:58 ` Jan Kybic [this message]
2007-09-19 11:13 ` [Caml-list] Can coThreads be used for message passing architecture? Erik de Castro Lopo
2007-09-19 12:59 ` Zheng Li
2007-09-20 4:16 ` [Caml-list] " Jon Harrop
2007-09-20 6:11 ` Erik de Castro Lopo
2007-09-20 9:06 ` Zheng Li
2007-09-20 8:49 ` Zheng Li
2007-09-19 19:13 ` [Caml-list] Re: [ANN] coThreads 0.10 Vu Ngoc San
2007-09-19 20:10 ` Zheng Li
2007-09-20 0:50 ` [Caml-list] " skaller
2007-09-20 4:29 ` Erik de Castro Lopo
2007-09-20 7:11 ` skaller
2007-09-20 7:52 ` Erik de Castro Lopo
2007-09-20 8:37 ` Zheng Li
2007-09-20 10:43 ` [Caml-list] " skaller
2007-09-20 10:44 ` Matthew Hannigan
2007-09-20 15:02 ` skaller
2007-09-20 15:07 ` Christophe Raffalli
2007-09-20 15:51 ` skaller
2007-09-20 16:26 ` Florian Weimer
2007-09-20 17:37 ` Vincent Aravantinos
2007-09-21 16:33 ` readline license (was: [ANN] coThreads 0.10) Xavier Leroy
2007-09-21 17:11 ` [Caml-list] " Matthew William Cox
2007-09-21 18:05 ` skaller
2007-09-21 21:51 ` [Caml-list] Re: readline license Markus E L
2007-09-21 22:16 ` Daniel Bünzli
2007-09-22 0:49 ` [Caml-list] Re: readline license (was: [ANN] coThreads 0.10) Matthew Hannigan
2007-09-20 11:39 ` [Caml-list] Re: [ANN] coThreads 0.10 Florian Weimer
2007-09-20 15:46 ` skaller
2007-09-20 18:14 ` Ken Rose
2007-09-20 8:31 ` Zheng Li
2007-09-20 8:18 ` Zheng Li
2007-09-18 2:10 ` [Caml-list] " Erik de Castro Lopo
2007-09-18 5:59 ` skaller
2007-09-18 6:23 ` Erik de Castro Lopo
2007-09-18 9:01 ` Zheng Li
2007-09-18 13:40 ` Zheng Li
2007-09-18 23:53 ` [Caml-list] " Erik de Castro Lopo
2007-09-18 9:09 ` [Caml-list] " skaller
2007-09-18 13:03 ` Markus E L
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=87ps0e9b1m.fsf_-_@fel.cvut.cz \
--to=kybic@fel.cvut.cz \
--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