From: Darren Wise <darren@wisecorp.co.uk>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] Plan9 usage but used to parallel MPI on linux..
Date: Mon, 31 Oct 2016 00:33:14 +0000 [thread overview]
Message-ID: <01j6686t81qlbfuv6p2rdy1t.1477873950110@email.android.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
Heya folks,
Can anyone point me in the right direction of some manuals concerning the use of a beowulf cluster style of computing setup, i'm so used to MPI installs and limiting myself to terminals that being what it seems ooout-f-he-box this already is setup with parallel computing in mind..
Also some examples would be great of common current usages of such.
> Kind regards,
> Darren Wise Esq,
> B.Sc, HND, GNVQ, City & Guilds.
>
> Managing Director (MD)
> Art Director (AD)
> Chief Architect/Analyst (CA/A)
> Chief Technical Officer (CTO)
>
> www.wisecorp.co.uk> www.wisecorp.co.uk/babywise
> www.darrenwise.co.uk
[-- Attachment #2: Type: text/html, Size: 1226 bytes --]
next reply other threads:[~2016-10-31 0:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 0:33 Darren Wise [this message]
2016-10-31 2:01 ` Chris McGee
2016-10-31 10:18 Richard Miller
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=01j6686t81qlbfuv6p2rdy1t.1477873950110@email.android.com \
--to=darren@wisecorp.co.uk \
--cc=9fans@9fans.net \
/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).