From: ron minnich <rminnich@lanl.gov>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] parallel programming in Plan 9
Date: Thu, 19 Feb 2004 07:35:04 -0700 [thread overview]
Message-ID: <Pine.LNX.4.44.0402190722530.32145-100000@maxroach.lanl.gov> (raw)
In-Reply-To: <fe25c680965a2bf7e824e5af346f7180@plan9.ucalgary.ca>
For grid, David Abrahamson tells us that the users want a simple
open/read/write/close interface for their apps. They want to name and open
net connections with the same ease that they name and open files. They
want to substitute files for net connections for testing. They don't want
to have to use gridFTP or similar kludges for getting to files; they want
the files to be accessible whereever they are. They have no particular
love of complex components and C++.
These user wants are of course in complete opposition to what CS people
want to provide for the grid. "I'm from the CS dept. and I'm here to
help".
When we looked at what the users wanted, as opposed to what the CS
researchers were planning to provide, we realized that Plan 9 fit the user
needs for Grid very well indeed, which is what got us started trying to
build the 9grid in the first place.
Don't assume that because MPI is ubiquotous that everyone wants it either.
They just assume that it's all they are going to get. Personally, I don't
exactly love MPI.
For on-machine cases, rfork with RFMEM will get you pretty far for
parallel programming. See the 'cpu' command for an example of using
shared-memory semaphores.
ron
next prev parent reply other threads:[~2004-02-19 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-18 21:02 James Horey
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 [this message]
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=Pine.LNX.4.44.0402190722530.32145-100000@maxroach.lanl.gov \
--to=rminnich@lanl.gov \
--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).