caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: Where's my non-classical shared memory	concurrency technology?
Date: Mon, 26 May 2008 17:08:16 +0100	[thread overview]
Message-ID: <200805261708.16457.jon@ffconsultancy.com> (raw)
In-Reply-To: <4EDC5A3B-DFD2-47EA-9C22-F0B355D7BBC7@inria.fr>

On Monday 26 May 2008 16:29:53 Damien Doligez wrote:
> On 2008-05-21, at 10:06, Martin Berger wrote:
> > Here I disagree. Shared  memory concurrency is a specific form
> > of message passing: Writing to a memory cell is in fact sending
> > a message to that cell carrying two items, the new value and a
> > return channel that is used to inform the writer that sending
> > has succeeded, and likewise for reading.
>
> This is completely wrong.  A few machines have a simple model like
> that, but they were all built in the last century.  Nowadays, writing
> to memory is more like broadcasting a message and having no idea when
> it will arrive at each destination.  And if you write to another piece
> of memory, you don't know in what order the updates will become
> visible to a given processor.
>
> You are neglecting a very important parameter, which is called the
> "memory model" of your multiprocessor.

The memory model of a multiprocessor is just a specific form of communication 
fabric. That does not disagree with Martin's statement. So he was certainly 
not "completely wrong". At worst it was a simplification. I suspect he simply 
did not aticipate anyone treating his comment as a seminal work on multicore 
computing.

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?e


  reply	other threads:[~2008-05-26 16:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-18  8:39 Berke Durak
2008-05-18 16:35 ` Jon Harrop
2008-05-19 11:45   ` [Caml-list] " Martin Berger
2008-05-19 12:24     ` Berke Durak
2008-05-19 21:47       ` Jon Harrop
2008-05-19 22:24         ` Berke Durak
2008-05-19 22:37           ` Raoul Duke
2008-05-20  0:04             ` Pierre-Evariste Dagand
2008-05-20 21:27           ` David Teller
2008-05-21  7:52             ` Martin Berger
2008-05-21  8:06       ` Martin Berger
2008-05-19 14:09     ` Gerd Stolpmann
2008-05-19 16:30       ` Richard Jones
2008-05-19 18:26       ` Jon Harrop
2008-05-20  7:40       ` Ulf Wiger (TN/EAB)
2008-05-21  8:18         ` Martin Berger
2008-05-21  8:06       ` Martin Berger
2008-05-21 13:50         ` Gerd Stolpmann
2008-05-26 15:29         ` Damien Doligez
2008-05-26 16:08           ` Jon Harrop [this message]
2008-05-27  9:34           ` Martin Berger
2008-05-28 11:18             ` Damien Doligez
2008-05-28 12:16               ` Jon Harrop
2008-05-28 17:41               ` Martin Berger
2008-05-29 12:02               ` Frédéric Gava

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=200805261708.16457.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.com \
    --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;
as well as URLs for NNTP newsgroup(s).