From: Jon Harrop <jonathandeanharrop@googlemail.com>
To: "'Gerd Stolpmann'" <info@gerd-stolpmann.de>
Cc: <caml-list@inria.fr>
Subject: RE: [Caml-list] Efficient OCaml multicore -- roadmap?
Date: Wed, 20 Apr 2011 22:44:38 +0100 [thread overview]
Message-ID: <02ac01cbffa4$2721b130$75651390$@ffconsultancy.com> (raw)
In-Reply-To: <1301084818.8429.435.camel@thinkpad>
Gerd wrote:
> When you implement a message passing API for a high level language, the way
> to go is to provide message buffers in memory. When a thread delivers a
> message it just writes to the buffer. The real message, however, is sent by the
> hardware under the hood, and must be delivered until the reading thread
> synchronizes. The point is here, IMHO, that you exploit the features of the
> hardware the most when you do it in a way the hardware can deal best with.
> Thus a program written against the message passing API will finally be faster
> than one that uncritically assumes a uniform memory, and modifies memory in-
> place, and will finally suffer from cache line bouncing.
I think we should work through a concrete example like the one Hugo gave using message passing and the other approaches to multicore parallelism. The following F# function "f" takes "tree" and creates "n" derivative data structures by applying "g" to it and then applies "h" to it in order to perform the "subsequent processing":
# let f tree n g h = Array.Parallel.init n (fun i -> h(g i tree))
val f : 'a -> int -> (int -> 'a -> 'b) -> ('b -> 'c) -> 'c array
For example, take the set {2,4,6,8} and add each of 0..9 and then count the number of elements:
# f (set[2;4;6;8]) 10 Set.add Set.count;;
- : int array = [|5; 5; 4; 5; 4; 5; 4; 5; 4; 5|]
Try to solve the same problem using explicit message passing.
> For current standard server hardware there are usually not enough CPUs to get a
> big effect. But in a few years it will be very important (as it is for current
> supercomputers), maybe even for standard 128 core laptops in 2015 (just
> guessing).
This needs quantifying. Dual core desktops became available with AMD's Athlon 64 X2 in 2005. Six years later, the widest multicore desktop Dell sells has only 6 cores and the widest server has only 12 cores (per CPU). If the trend continues, we'll barely have 18-core desktops by 2015 much less 128-core laptops.
Cheers,
Jon.
next prev parent reply other threads:[~2011-04-20 21:45 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2054357367.219171.1300974318806.JavaMail.root@zmbs4.inria.fr>
2011-03-24 23:13 ` Fabrice Le Fessant
2011-03-25 0:23 ` [Caml-list] " Sylvain Le Gall
2011-03-25 9:55 ` [Caml-list] " Alain Frisch
2011-03-25 11:44 ` Gerd Stolpmann
[not found] ` <1396338209.232813.1301046980856.JavaMail.root@zmbs4.inria.fr>
2011-03-25 10:23 ` Fabrice Le Fessant
2011-03-25 12:07 ` Gerd Stolpmann
2011-04-16 12:12 ` Jon Harrop
2011-03-25 10:51 ` Hugo Ferreira
2011-03-25 12:25 ` Gerd Stolpmann
2011-03-25 12:58 ` Hugo Ferreira
[not found] ` <341494683.237537.1301057887481.JavaMail.root@zmbs4.inria.fr>
2011-03-25 13:10 ` Fabrice Le Fessant
2011-03-25 13:41 ` Dario Teixeira
2011-03-30 18:12 ` Jon Harrop
2011-03-25 15:44 ` Hugo Ferreira
2011-03-25 18:24 ` Martin Jambon
2011-03-25 19:19 ` Hugo Ferreira
2011-03-25 20:26 ` Gerd Stolpmann
2011-03-26 9:11 ` Hugo Ferreira
2011-03-26 10:31 ` Richard W.M. Jones
2011-03-30 16:56 ` Jon Harrop
2011-03-30 19:24 ` Richard W.M. Jones
2011-04-20 21:44 ` Jon Harrop [this message]
2011-04-19 9:57 ` Eray Ozkural
2011-04-19 10:05 ` Hugo Ferreira
2011-04-19 20:26 ` Gerd Stolpmann
2011-04-20 7:59 ` Hugo Ferreira
2011-04-20 12:30 ` Markus Mottl
2011-04-20 12:53 ` Hugo Ferreira
2011-04-20 13:22 ` Markus Mottl
2011-04-20 14:00 ` Edgar Friendly
2011-04-19 22:49 ` Jon Harrop
2011-03-30 17:02 ` Jon Harrop
2011-04-20 19:23 ` Jon Harrop
2011-04-20 20:05 ` Alexy Khrabrov
2011-04-20 23:00 ` Jon Harrop
[not found] ` <76544177.594058.1303341821437.JavaMail.root@zmbs4.inria.fr>
2011-04-21 7:48 ` Fabrice Le Fessant
2011-04-21 8:35 ` Hugo Ferreira
2011-04-23 17:32 ` Jon Harrop
2011-04-21 9:09 ` Alain Frisch
[not found] ` <799994864.610698.1303412613509.JavaMail.root@zmbs4.inria.fr>
2011-04-22 8:06 ` Fabrice Le Fessant
2011-04-22 9:11 ` Gerd Stolpmann
2011-04-23 10:17 ` Eray Ozkural
2011-04-23 13:47 ` Alexy Khrabrov
2011-04-23 17:39 ` Eray Ozkural
2011-04-23 20:18 ` Alexy Khrabrov
2011-04-23 21:18 ` Jon Harrop
2011-04-24 0:33 ` Eray Ozkural
2011-04-28 14:42 ` orbitz
2011-04-23 19:02 ` Jon Harrop
2011-04-22 9:44 ` Vincent Aravantinos
[not found] ` <20110421.210304.1267840107736400776.Christophe.Troestler+ocaml@umons.ac.be>
2011-04-21 19:53 ` Hezekiah M. Carty
2011-04-22 8:34 ` Alain Frisch
2011-04-21 10:09 ` Philippe Strauss
2011-04-23 17:44 ` Jon Harrop
2011-04-23 17:05 ` Jon Harrop
2011-04-20 20:30 ` Gerd Stolpmann
2011-04-20 23:33 ` Jon Harrop
2011-03-25 20:27 ` Philippe Strauss
2011-04-19 22:47 ` Jon Harrop
[not found] ` <869445701.579183.1303253283515.JavaMail.root@zmbs4.inria.fr>
2011-04-20 9:25 ` Fabrice Le Fessant
2011-03-25 18:45 ` Andrei Formiga
2011-03-30 17:00 ` Jon Harrop
2011-04-13 3:36 ` Lucas Dixon
2011-04-13 13:01 ` Gerd Stolpmann
2011-04-13 13:09 ` Lucas Dixon
2011-04-13 23:04 ` Goswin von Brederlow
2011-04-16 13:54 ` Jon Harrop
2011-03-24 13:44 Alexy Khrabrov
2011-03-24 14:57 ` Gerd Stolpmann
2011-03-24 15:03 ` Joel Reymont
2011-03-24 15:28 ` Guillaume Yziquel
2011-03-24 15:48 ` Gerd Stolpmann
2011-03-24 15:38 ` Gerd Stolpmann
2011-03-25 19:49 ` Richard W.M. Jones
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='02ac01cbffa4$2721b130$75651390$@ffconsultancy.com' \
--to=jonathandeanharrop@googlemail.com \
--cc=caml-list@inria.fr \
--cc=info@gerd-stolpmann.de \
/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