caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Richard W.M. Jones" <rich@annexia.org>
To: Alexy Khrabrov <deliverable@gmail.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] walking a graph in parallel
Date: Wed, 30 Mar 2011 20:36:49 +0100	[thread overview]
Message-ID: <20110330193649.GA4644@annexia.org> (raw)
In-Reply-To: <3CE6E368-B103-472C-B622-672616E7CAB8@gmail.com>

On Tue, Mar 29, 2011 at 06:56:28PM -0400, Alexy Khrabrov wrote:
> Or, is it possible to use a huge chunk of shared memory, to place
> the read-only graph there and query it somehow separately from each
> worker, then use 0MQ for the reduce communication phase?

As it's read-only, sounds like an ideal application for ancient:

http://git.annexia.org/?p=ocaml-ancient.git;a=summary

Rich.

-- 
Richard Jones
Red Hat

      parent reply	other threads:[~2011-03-30 19:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 22:56 Alexy Khrabrov
2011-03-30  0:35 ` Gerd Stolpmann
2011-03-30 19:36 ` Richard W.M. Jones [this message]

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=20110330193649.GA4644@annexia.org \
    --to=rich@annexia.org \
    --cc=caml-list@inria.fr \
    --cc=deliverable@gmail.com \
    /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).