From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82]) by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id p3JMo0a4019278 for ; Wed, 20 Apr 2011 00:50:03 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: An0CAMgQrk1KfVI0kGdsb2JhbACEUKBgCBQBAQEBCQkNBxQEIakkijiCYQEFjkQBBIEpg056mAE6 X-IronPort-AV: E=Sophos;i="4.64,241,1301868000"; d="scan'208";a="106282696" Received: from mail-ww0-f52.google.com ([74.125.82.52]) by mail1-smtp-roc.national.inria.fr with ESMTP/TLS/RC4-SHA; 20 Apr 2011 00:50:03 +0200 Received: by wwe15 with SMTP id 15so265727wwe.9 for ; Tue, 19 Apr 2011 15:50:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:from:to:cc:references:in-reply-to:subject:date :organization:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:content-language; bh=pc3a07qGCtZTw/Vazu2bW+Sd4FwApP+X/FsLdY9xAWw=; b=BuBWo5nDoohIOBXcV3QCEpxWk5I+UCQ3Rwb6BYOhAa6m/eh+KkWbVvKCvfa1jYKiew nd/j0xYPbS4h8U6I/GMzT0cPMajXVGERgxNhFn02wdBjNiTCqNVnpoHGkglGxrQzYI7B tLak3g0gb6nJgV6lQsWE+MkHwHipwWLnAU2tg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=from:to:cc:references:in-reply-to:subject:date:organization :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:content-language; b=sHmDAIgp5jhh/rviTUCxChGa4nzPd28ZOKMEcDfbvkpk4aqnt6z02Sy0SSTngkG3f3 TG/E0+A9eukAohBdXS0rpS9jNTR7f8TNmTlauvTewdRJnPAeW4JlTP9qkOPYNDXjJAZD bOAIRQu7zYngLmw3XEE6LymWiRBp7sKDeSqQ8= Received: by 10.216.65.142 with SMTP id f14mr926683wed.2.1303253402933; Tue, 19 Apr 2011 15:50:02 -0700 (PDT) Received: from WinEight ([80.229.123.248]) by mx.google.com with ESMTPS id r80sm176603wei.15.2011.04.19.15.50.01 (version=SSLv3 cipher=OTHER); Tue, 19 Apr 2011 15:50:02 -0700 (PDT) From: Jon Harrop To: "'Hugo Ferreira'" Cc: References: <2054357367.219171.1300974318806.JavaMail.root@zmbs4.inria.fr> <4D8BD02D.1010505@inria.fr> <4D8C73C8.6020801@inescporto.pt> <1301055903.8429.314.camel@thinkpad> <341494683.237537.1301057887481.JavaMail.root@zmbs4.inria.fr> <4D8C944A.9060601@inria.fr> <4D8CB859.9040709@inescporto.pt> <4D8CDDCC.4010000@ens-lyon.org> <4D8CEAA4.2030403@inescporto.pt> In-Reply-To: <4D8CEAA4.2030403@inescporto.pt> Date: Tue, 19 Apr 2011 23:49:51 +0100 Organization: Flying Frog Consultancy Message-ID: <022501cbfee4$18a0c8a0$49e259e0$@ffconsultancy.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQFhMASujb2QG2h3N2h7/lJjoQ23OAIYQRkZAge6bucBi7oV8gIGVE8/AmcCvngCudDnUAFa0vZTARTLcbCUwUZogA== Content-Language: en-gb Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by walapai.inria.fr id p3JMo0a4019278 X-Validation-by: jon@ffconsultancy.com Subject: RE: [Caml-list] Efficient OCaml multicore -- roadmap? Huge wrote: > Cannot see how this works. Say I want to share a balanced binary tree. > Several processes/threads each take this tree and alter it by adding and deleting > elements. Each (new) tree is then further processed by other processes/threads. Note that you don't want to manipulate a tree on one thread and then pass it to another for processing because the threads are likely to be running on different cores and you will be needlessly moving the tree from one core's cache to another core's cache. Better that any given core runs the different algorithms on the same data to reduce communication. Cheers, Jon.