From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jhc0033@gmail.com>
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr
X-Spam-Level: **
X-Spam-Status: No, score=2.8 required=5.0 tests=DNS_FROM_RFC_POST,SPF_NEUTRAL 
	autolearn=disabled version=3.1.3
X-Original-To: caml-list@yquem.inria.fr
Delivered-To: caml-list@yquem.inria.fr
Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105])
	by yquem.inria.fr (Postfix) with ESMTP id 9A043BB84
	for <caml-list@yquem.inria.fr>; Mon, 14 Jul 2008 13:32:55 +0200 (CEST)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ArEFAE3WekhKfS4cbGdsb2JhbACRakMQBAQaA5FHhFM
X-IronPort-AV: E=Sophos;i="4.30,359,1212357600"; 
   d="scan'208";a="27303213"
Received: from yw-out-2324.google.com ([74.125.46.28])
  by mail4-smtp-sop.national.inria.fr with ESMTP; 14 Jul 2008 13:32:55 +0200
Received: by yw-out-2324.google.com with SMTP id 5so2143458ywb.3
        for <caml-list@yquem.inria.fr>; Mon, 14 Jul 2008 04:32:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to
         :subject:in-reply-to:mime-version:content-type
         :content-transfer-encoding:content-disposition:references;
        bh=1CozheFhy+f7fM1ZEnC4k6le08Gi0dAoVrzXjxnV4Yc=;
        b=CpfOoxylxOB30Q3IhhXin/Hkyw+t0U/KMolPDAn/SL5qUcC2MOM+JXE3UW+9Vfq7pS
         u2KLxBosPLst+tyTklcUXHEkfVSK0kNL133ZR2JHvUzmBuOPYVsToKhKEYmZs8y1+aYe
         AXpy2KW5S7RMEexelvFNZx0RFTKNsTP1F3S1E=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=nQl9/D08r86uMGv1+d5K+PeDV8jc9YS4J4Q6HurSzHSgqxSLhA8j5gBTr2HWfJOu3l
         ofGVf6SjMn2S3jVjuTCuOL8ISPlSGOjpHI5N+y/6KhjigjV6ZakWbXYOoih/rpaYEZ84
         L/3YA9R13v+unvmWDg4PWW15ZPcOCbmoURC8M=
Received: by 10.115.89.1 with SMTP id r1mr17420719wal.12.1216035173332;
        Mon, 14 Jul 2008 04:32:53 -0700 (PDT)
Received: by 10.114.147.12 with HTTP; Mon, 14 Jul 2008 04:32:53 -0700 (PDT)
Message-ID: <c6c368760807140432i2283a487q8f07416efc81e6be@mail.gmail.com>
Date: Mon, 14 Jul 2008 04:32:53 -0700
From: "J C" <jhc0033@gmail.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] thousands of CPU cores
In-Reply-To: <200807101235.42602.jon@ffconsultancy.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <c6c368760807092257v7a125fey534fbc6d5444d14@mail.gmail.com>
	 <200807101235.42602.jon@ffconsultancy.com>
X-Spam: no; 0.00; ocaml:01 openmp:01 parallelism:01 openmp:01 ocamlmpi:01 ocaml:01 jhc:98 0033:98 10,:98 threads:01 wrote:01 caml-list:01 api:02 confusing:02 native:03 

On Thu, Jul 10, 2008 at 4:35 AM, Jon Harrop <jon@ffconsultancy.com> wrote:

> OCaml already has OS native threads (albeit with a global lock), already
> supports OpenMP and can already be used to write parallel programs that
> exploit multiple cores.
>
> ...
> Incidentally, MP is good for distributed parallelism but fails to take
> advantage of shared memory (with a concurrent GC).

I think you are confusing stuff. OpenMP is a shared-memory API, MPI is
a message-passing interface, OpenMPI is one implementation of the
latter, OCamlMPI is another. OCaml has little to do with OpenMP
though. Am I wrong?