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: Wed, 28 May 2008 13:16:54 +0100 [thread overview]
Message-ID: <200805281316.54628.jon@ffconsultancy.com> (raw)
In-Reply-To: <CF949D11-6284-4416-ADFE-80A3B4685BB8@inria.fr>
On Wednesday 28 May 2008 12:18:37 Damien Doligez wrote:
> On 2008-05-27, at 11:34, 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.
>
> [...]
>
> > But broadcasting is a form of message-passing too!
>
> That wasn't my point. My point was that there is no return channel.
> If you want to know when your write is done, you have to use a lock
> or a memory barrier. Both are very expensive.
Very expensive compared to what?
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?e
next prev parent reply other threads:[~2008-05-28 12:21 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
2008-05-27 9:34 ` Martin Berger
2008-05-28 11:18 ` Damien Doligez
2008-05-28 12:16 ` Jon Harrop [this message]
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=200805281316.54628.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