Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jonathan Bryant <jtbryant@valdosta.edu>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Faking concurrency using Unix forks and pipes
Date: Wed, 30 May 2007 00:12:51 -0400	[thread overview]
Message-ID: <3957E93F-A8E0-44F5-98F2-8730FD70ABFA@valdosta.edu> (raw)
In-Reply-To: <200705300442.59906.jon@ffconsultancy.com>


On May 29, 2007, at 11:42 PM, Jon Harrop wrote:

>
> Has anyone implemented a parallel map function in OCaml using Unix  
> forks,
> pipes and maybe marshalling?

I've implemented a toy version of this, so I can say it does work and  
is not too hard, although I don't still have the code.  My OSP  
project is a concurrency library that would make implementing this  
pretty trivial though: it extends the Event module to work over UNIX  
& TCP sockets and to have a common interface for thread creation /  
forking / remote process creation.

>
> This seems like an easy way to get concurrency in OCaml...

It would also be nice to have a Apply in Parallel / Parallel List  
Comprehension syntax for it a la NESL (http://www.cs.cmu.edu/~scandal/ 
nesl.html).

>
> -- 
> Dr Jon D Harrop, Flying Frog Consultancy Ltd.
> OCaml for Scientists
> http://www.ffconsultancy.com/products/ocaml_for_scientists/?e
>
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs


  parent reply	other threads:[~2007-05-30  4:14 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30  3:42 Jon Harrop
2007-05-30  4:10 ` [Caml-list] " Erik de Castro Lopo
2007-05-30  4:12 ` Jonathan Bryant [this message]
2007-05-30  9:45   ` Benedikt Grundmann
2007-05-30  7:02 ` Oliver Bandel
2007-05-30  7:31   ` Jon Harrop
2007-05-30 16:22     ` David Teller
2007-05-30  7:34   ` Loup Vaillant
2007-05-30  8:02     ` Jon Harrop
2007-05-30  8:13       ` Erik de Castro Lopo
2007-05-30  8:30         ` Loup Vaillant
2007-05-30  8:32           ` Loup Vaillant
2007-05-30  8:50             ` Jon Harrop
2007-05-30 12:13               ` Richard Jones
2007-05-30  8:54         ` Jon Harrop
2007-05-30  9:56           ` Mattias Engdegård
2007-05-30 12:15           ` Richard Jones
2007-05-30 17:46           ` Pablo Polvorin
2007-05-30 19:14           ` Erik de Castro Lopo
2007-05-30  7:13 ` Florian Hars
2007-05-30 11:31   ` Gerd Stolpmann
2007-05-30  8:40 ` Luc Maranget
2007-05-30  9:10   ` Erik de Castro Lopo
2007-05-30  9:25     ` Erik de Castro Lopo
2007-05-30  9:25       ` Jon Harrop
2007-05-30  9:41         ` Joel Reymont
2007-05-30 16:05         ` David Teller
2007-05-30  9:21   ` Joel Reymont
2007-05-30 16:10   ` David Teller
2007-05-30  9:52 ` Thomas Fischbacher
2007-05-30 12:03 ` Richard Jones
2007-05-30 16:03 ` Granicz Adam
2007-05-30 22:09   ` Jon Harrop
     [not found] <5F7D2956-2B0A-465A-8AC2-06D7EDC457F9@valdosta.edu>
2007-05-30 19:44 ` Fwd: " Jonathan Bryant
2007-05-30 19:57   ` Erik de Castro Lopo
2007-05-30 20:05     ` Jonathan Bryant
2007-05-30 22:08       ` Jon Harrop

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=3957E93F-A8E0-44F5-98F2-8730FD70ABFA@valdosta.edu \
    --to=jtbryant@valdosta.edu \
    --cc=caml-list@yquem.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