caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Mohamed Iguernlala <iguer.auto@gmail.com>
To: caml-list@inria.fr
Subject: Re: [Caml-list] muti-core programming
Date: Wed, 9 Mar 2016 11:23:31 +0100	[thread overview]
Message-ID: <56DFF9A3.4040805@gmail.com> (raw)
In-Reply-To: <56DFF5E5.1050109@inria.fr>

Hi,

Functory may be suitable as well 
(http://opam.ocaml.org/packages/functory/functory.0.5/)

--
Mohamed Iguernlala.
Senior R&D Engineer, OCamlPro SAS
Research Associate, VALS team, LRI

Le 09/03/2016 11:07, Francois Berenger a écrit :
> On 03/09/2016 10:50 AM, 刘坚 wrote:
>> Hi,
>>
>>           I’m recently writing a formal verification tool in OCaml, and
>> it works really well, but I’m considering writing a concurrent version.
>> However, until now, there seems to be no way to write programs that take
>> advantage of multi-cores.
>
> To accelerate something, probably you want paralellism, not concurrency.
>
> I recomend parmap, but there are some other libraries out there
> too for that purpose (in opam: forkwork and probably others I don't 
> know).
>
> But be careful that too fine granularity calculations don't 
> parallelize well.
> For example, if you are analyzing source code, maybe analyzing
> distinct files in parallel would be a coarse enough granularity.
>
> > So, I’m wondering when will OCaml support
>> multi-core programming? Or else, do I have other choices by using some
>> external extensions of OCaml instead of the standard library?
>>
>> Thanks,
>>
>> Jian
>


  reply	other threads:[~2016-03-09 10:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09  9:50 刘坚
2016-03-09 10:07 ` Francois Berenger
2016-03-09 10:23   ` Mohamed Iguernlala [this message]
2016-03-09 11:04     ` Francois Berenger
2016-03-09 21:58       ` Yaron Minsky

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=56DFF9A3.4040805@gmail.com \
    --to=iguer.auto@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).