From: "Roman V. Shaposhnik" <rvs@sun.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 on Blue Gene
Date: Wed, 30 Jul 2008 05:32:00 -0700 [thread overview]
Message-ID: <1217421120.5036.34.camel@goose.sun.com> (raw)
In-Reply-To: <a4e6962a0807261147m7f0ec046xaac96ee2b53c0eb4@mail.gmail.com>
On Sat, 2008-07-26 at 13:47 -0500, Eric Van Hensbergen wrote:
> On Sat, Jul 26, 2008 at 1:37 PM, Steven Vormwald <sdvormwa@mtu.edu> wrote:
> > Is there any (public) information about how plan 9 is/was being used on Blue
> > Gene? The only information I can find seems to be "press release"-type
> > papers that just say that it runs on Blue Gene, but not what it was used for
> > nor how it was setup and used.
> >
>
> The existing BG/L port was a prototype proof of concept. It was not
> done in a clean-room fashion and so large portions of it are not
> releasable. The proof of concept was done as part of a proposal to a
> DOE funded project which just got under way. As part of that project
> which is funded for the next three years, we'll be doing a "clean"
> port to the BG/P (which will be open sourced) along with using Plan 9
> to explore large scale (tens of thousands of nodes) distributed
> systems. High level details are available off of the IBM Research
> pages: http://domino.research.ibm.com/comm/research_projects.nsf/pages/hare.index.html
> -- more detailed information to come.
Do you have any bits and pieces of the software ecosystem not
readily available on Plan9 (dreadful things like a C++ compiler)
covered by these funds or is your intention to use available
Plan9 userland as-is?
Thanks,
Roman.
next prev parent reply other threads:[~2008-07-30 12:32 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-26 18:37 Steven Vormwald
2008-07-26 18:47 ` Eric Van Hensbergen
2008-07-30 12:32 ` Roman V. Shaposhnik [this message]
2008-07-30 14:07 ` Eric Van Hensbergen
2008-07-30 15:10 ` ron minnich
2008-07-30 15:21 ` Steven D. Vormwald
2008-07-30 15:38 ` Eric Van Hensbergen
2008-07-30 15:41 ` ron minnich
2008-07-30 16:10 ` Steven D. Vormwald
2008-07-30 17:42 ` ron minnich
2008-07-30 17:52 ` Steven D. Vormwald
2008-07-31 21:32 ` Charles Forsyth
2008-07-30 16:34 ` Joel C. Salomon
2008-07-30 15:25 ` gdiaz
2008-07-30 15:36 ` Eric Van Hensbergen
2008-07-30 23:36 ` David Leimbach
2008-07-31 0:02 ` ron minnich
2008-07-31 0:45 ` erik quanstrom
2008-07-31 1:48 ` David Leimbach
2008-07-31 2:23 ` ron minnich
2008-07-31 12:53 ` Philippe Anel
2008-07-31 13:35 ` David Leimbach
2008-07-31 14:11 ` Philippe Anel
2008-07-31 14:32 ` David Leimbach
2008-07-31 16:04 ` ron minnich
2008-08-04 23:19 ` Uriel
2008-07-31 13:24 ` gdiaz
2008-07-31 13:24 ` gdiaz
2008-07-30 15:40 ` ron minnich
2008-07-30 17:36 ` don bailey
2008-07-30 17:39 ` Benjamin Huntsman
2008-07-30 17:47 ` ron minnich
2008-07-30 18:03 ` don bailey
2008-07-30 18:08 ` Eric Van Hensbergen
2008-07-30 18:18 ` ron minnich
2008-07-30 18:21 ` erik quanstrom
2008-07-30 18:32 ` ron minnich
2008-07-31 22:03 ` Charles Forsyth
2008-07-31 22:06 ` ron minnich
2008-07-31 21:27 ` Charles Forsyth
2008-07-30 15:43 ` Jack Johnson
2008-07-31 14:01 erik quanstrom
[not found] <2049e07e918215a675b00f15ee549436@quanstro.net>
2008-07-31 14:28 ` David Leimbach
2008-07-31 15:20 ` erik quanstrom
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=1217421120.5036.34.camel@goose.sun.com \
--to=rvs@sun.com \
--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).