9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "David Leimbach" <leimy2k@gmail.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 08:32:18 -0700	[thread overview]
Message-ID: <3e1162e60807140832u5df4ae00hae1ff467ef0b6b0b@mail.gmail.com> (raw)
In-Reply-To: <d08d7019-7b25-4f0f-a07e-840d94591f4f@m44g2000hsc.googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 1436 bytes --]

On Mon, Jul 14, 2008 at 1:45 AM, ssecorp <circularfunc@gmail.com> 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?
>
> In what way does it make it easy?
>
> Assuming that the kernel can address multiple cores and SMP systems (I've
never tried it but I assume it can), one can write code in C via a library
called libthread, which provides a mechanism for writing concurrent programs
(originally meant to help port the programs written in the ill-fated but
very cool language Alef to C).
It features threads and typed data channels for interprocess communication
in a CSP sort of organization.

If libthread is able to grab real processors per thread and get them
scheduled, one's concurrent style code ultimately ends up having potential
to run in parallel on those cores/processors.

I think this method of writing programs designed to work on multi-core
systems is a good one.  As do the folks who use Concurrent Haskell, or even
Erlang and perhaps Scala and other "new languages".  In a sense this makes
writing code for multiple cores "easy" on Plan 9.

Dave

[-- Attachment #2: Type: text/html, Size: 1808 bytes --]

  parent reply	other threads:[~2008-07-14 15:32 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 [this message]
2008-07-14 16:00   ` erik quanstrom
2008-07-14 16:29 ` Roman V. Shaposhnik
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=3e1162e60807140832u5df4ae00hae1ff467ef0b6b0b@mail.gmail.com \
    --to=leimy2k@gmail.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).