From: "Campbell, Marc" <CAMPBMA1@mail.northgrum.com>
To: "Robert G. Werner" <rwerner@lx1.microbsys.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: PowerPC Beowulf Who?
Date: Tue, 23 Feb 1999 17:13:39 -0500 [thread overview]
Message-ID: <36D3280F.6A8B241A@mail.northgrum.com> (raw)
In-Reply-To: Pine.LNX.3.96.990222221152.1258A-100000@lx1.microbsys.com
There are several issues. Some PPC specific and some not.
General issues would include the ability to procure turn key system and software revision support.
PPC specific issues start with the assurance that the necessary libs (e.g. MPI) have been checked out on PPC hardware clusters.
Another PPC issue is cluster communication. In some cases standard ethernet is not enough cluster bandwidth. In what case does FireWire make sense in a PPC Beowulf (Linux) cluster? Is Myrinet (www.myri.com) a more appropriate clustering communication system? If Myrinet, then where are the LinuxPPC or YDL drivers? Myrinet lists Alpha Linux and x86 Linux but NOT PPC Linux (http://www.myri.com:80/GM/).
Who is taking initiative in the PowerPC/AltiVec Beowulf (Linux clustering) area?
-- Marc
Marc Campbell
Northrop Grumman
Technology Development
High Performance Computing, Group Lead
Melbourne, FL
campbma1@mail.northgrum.com
"Robert G. Werner" wrote:
> Are the issues that different for PPC than for the other architectures that you
> need to special attention on this matter? My understanding was that the
> clustering techniques used for Beowulf were based on standard libs (PVM,
> IIRC). Thus the issues seem like they should be pretty much the same as on any
> other HW baring Networking HW questions.
> Am I way off base here?
>
> Robert G. Werner
> rwerner@lx1.microbsys.com
> Impeach Conggress!!
>
> To believe your own thought, to believe that what is true for
> you in your private heart is true for all men -- that is genius.
> -- Ralph Waldo Emerson
>
> On Mon, 22 Feb 1999, Campbell, Marc wrote:
>
> >
> > Any suggestions on who to contact for PowerPC & PowerPC/AltiVec Beowulf development, integration, sales, and/or support?
> >
> > Marc Campbell
> > Northrop Grumman
> > Technology Development
> > High Performance Computing, Group Lead
> > Melbourne, FL
> >
> > campbma1@mail.northgrum.com
> >
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-02-23 22:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-22 17:35 PowerPC Beowulf Who? Campbell, Marc
1999-02-23 6:14 ` Robert G. Werner
1999-02-23 22:13 ` Campbell, Marc [this message]
1999-02-23 23:22 ` Robert G. Werner
1999-02-25 4:06 ` Troy Benjegerdes
1999-02-25 10:28 ` sean o'malley
1999-02-25 19:31 ` Robert G. Werner
1999-02-25 17:05 ` sean o'malley
1999-02-25 22:30 ` Robert G. Werner
1999-02-26 0:35 ` Nathan Hurst
1999-02-26 6:16 ` Troy Benjegerdes
1999-02-26 6:51 ` Cort Dougan
1999-02-26 2:56 ` Douglas Godfrey
1999-03-02 11:00 ` Martin Konold
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=36D3280F.6A8B241A@mail.northgrum.com \
--to=campbma1@mail.northgrum.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rwerner@lx1.microbsys.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).