caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Eray Ozkural <examachine@gmail.com>
To: Gaspard Bucher <gaspard@teti.ch>
Cc: David MENTRE <dmentre@linux-france.org>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ocaml for embedding
Date: Tue, 20 Jul 2010 03:36:18 +0300	[thread overview]
Message-ID: <AANLkTinhmDybCbXKTtyI53yzuOZKid4DC7t-grDrRGre@mail.gmail.com> (raw)
In-Reply-To: <AANLkTiltvIH58qPFuPZS3yRWwj5x2c3EJGTTVNjjPNQP@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 930 bytes --]

On Mon, Jul 12, 2010 at 4:19 PM, Gaspard Bucher <gaspard@teti.ch> wrote:

>  Just a final question on the topic: has JoCaml anything to do with
> this concurrency (shared memory) question ?


It seems to me that it can be implemented for a shared memory system. Why
not? But it's been designed with distributed memory in mind. So, I suppose
writing to shared memory could be slow. It'd be sort of like implementing
synchronization on top of a message passing system. Although I can see that
reading is OK. I would still like a nice and sound source-level support for
shared memory, if possible :) Do not all of us need such a feature? My cores
are idle. That's a pity. Yes, I did use ocamlmpi to get some speedup on
shared memory, but it's not the same thing. I shouldn't have to go back to
C++ just for implementing a shared memory algorithm.

Best,
-- 
Eray Ozkural, PhD candidate.  Comp. Sci. Dept., Bilkent University, Ankara

[-- Attachment #2: Type: text/html, Size: 1259 bytes --]

  reply	other threads:[~2010-07-20  0:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-08 21:02 Gaspard Bucher
2010-07-09  7:06 ` [Caml-list] " David MENTRE
2010-07-09 10:29   ` Gaspard Bucher
2010-07-12  9:14     ` David MENTRE
2010-07-12 13:19       ` Gaspard Bucher
2010-07-20  0:36         ` Eray Ozkural [this message]
2010-07-20 15:02           ` Eray Ozkural

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=AANLkTinhmDybCbXKTtyI53yzuOZKid4DC7t-grDrRGre@mail.gmail.com \
    --to=examachine@gmail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=dmentre@linux-france.org \
    --cc=gaspard@teti.ch \
    /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).