9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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 and multicores/parallelism/concurrency?
Date: Mon, 14 Jul 2008 09:29:22 -0700	[thread overview]
Message-ID: <1216052962.22701.26.camel@goose.sun.com> (raw)
In-Reply-To: <d08d7019-7b25-4f0f-a07e-840d94591f4f@m44g2000hsc.googlegroups.com>

On Mon, 2008-07-14 at 08:45 +0000, ssecorp wrote:
> from wikipedia:
> "Plan 9 from Bell Labs is a distributed operating system, primarily
> used for research."
>
> but it doesnt say anything more about the distributed part.
>
> I have recently found a big interest in concurrency, distributed
> systems and multicore-programming.
>
> So is Plan 9 good for a multicore-computer or what kind of distributed
> system is it made for?

I believe the real question is not whether Plan9 is good for multicore,
but whether multicore is any good as a long term computing strategy.

My personal impression has always been that Plan9 is the best OS for
distributed memory systems. I believe that folks working with IBM can
elaborate on that. As for the shared memory (whether NUMA or not) the
pressure is more on application (and thus application level languages
and tools) than on OS. It'll be interesting to see how a single Plan9
kernel scales on something like a Batoka box (256 hardware threads per
box, 64 physical cores). On the other hand, may be the trick is not
to scale a single kernel on something like that but have multiple
kernels running under something like Xen or kvm.

Thanks,
Roman.




  parent reply	other threads:[~2008-07-14 16:29 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14  8:45 ssecorp
2008-07-14  9:08 ` sqweek
2008-07-14 16:17   ` Iruata Souza
2008-07-14 16:31   ` Roman V. Shaposhnik
2008-07-14 10:15 ` a
2008-07-14 15:32 ` David Leimbach
2008-07-14 16:00   ` erik quanstrom
2008-07-14 16:29 ` Roman V. Shaposhnik [this message]
2008-07-14 20:08   ` a
2008-07-14 20:39     ` Roman V. Shaposhnik
2008-07-14 22:12       ` a
2008-07-17 12:26         ` Roman V. Shaposhnik
2008-07-17 12:40           ` erik quanstrom
2008-07-17 13:00             ` ron minnich
2008-07-14 20:43     ` Charles Forsyth
2008-07-14 16:35 erik quanstrom
     [not found] <f1209aefaab5eece7465c3d0df545ddd@quanstro.net>
2008-07-14 20:33 ` Roman V. Shaposhnik
2008-07-15  1:37   ` Joel C. Salomon
2008-07-15  8:01   ` Bakul Shah
2008-07-15 17:50     ` Paul Lalonde
2008-07-17 19:29       ` Bakul Shah
2008-07-18  3:31         ` Paul Lalonde

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=1216052962.22701.26.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).