From: James Horey <jhorey@unm.edu>
To: 9fans@cse.psu.edu
Subject: [9fans] parallel programming in Plan 9
Date: Wed, 18 Feb 2004 14:02:07 -0700 [thread overview]
Message-ID: <4033D2CF.3030208@unm.edu> (raw)
Hi,
Does someone mind explaining to me the advantages of using Plan 9 to
write/run parallel programs over say writing a "traditional" parallel
program using MPI? I read several things mentioning the higher
abstraction that private namespaces provide over explicit message
passing, but frankly I am not sure how to apply that idea efficiently to
remove explicit message passing. For instance, what would efficiently
replace MPI_Reduce? Also, I've briefly read something about Alef, but
there doesn't seem to be much talk about it. Is that language still
actively used in this community? Perhaps my brain isn't cooperating with
me today, so I would appreciate any help. Thanks!
-James Horey
next reply other threads:[~2004-02-18 21:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 21:02 James Horey [this message]
2004-02-18 21:17 ` Scott Schwartz
2004-02-18 22:36 ` James Horey
2004-02-18 22:52 ` David Presotto
2004-02-18 23:23 ` Scott Schwartz
2004-02-19 5:00 ` andrey mirtchovski
2004-02-19 14:35 ` ron minnich
2004-02-19 14:40 ` boyd, rounin
2004-02-18 21:17 David Presotto
2004-02-19 19:18 ` rog
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=4033D2CF.3030208@unm.edu \
--to=jhorey@unm.edu \
--cc=9fans@cse.psu.edu \
/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).