Plan 9 and multicores/parallelism/concurrency?
  Home FAQ Contact Sign in
comp.os.plan9 only
 
Advanced search
POPULAR GROUPS

more...

comp.os.plan9 Profile…
 Up
Plan 9 and multicores/parallelism/concurrency?         


Author: ssecorp
Date: Jul 14, 2008 01:45

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?
7 Comments
Re: [9fans] Plan 9 and multicores/parallelism/concurrency?         


Author: sqweek
Date: Jul 14, 2008 02:08

On Mon, Jul 14, 2008 at 4:45 PM, ssecorp 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.
>
> In what way does it make it easy?

Plan 9 makes it easy via 9p, its file system/resource sharing
protocol. In plan 9, things like graphics and network drivers export a
9p interface (a filetree). Furthermore, 9p is network transparent
which means accesses to remote resources look exactly like accesses to
local resources, and this is the main trick - processes do not care
whether the file they are interested in is being served by the kernel,
a userspace process, or a machine half way across the world.
-sqweek
2 Comments
Re: [9fans] Plan 9 and multicores/parallelism/concurrency?         


Author: a
Date: Jul 14, 2008 03:19

In addition to sqweek's good reply:
The "distributed" part also refers to how a typical installation is
structured. The system responsible for authenticating you, your
file server, the cpu server you run processes on, and the terminal
you're typing at may well all be distinct computers, but for the
most part none of the application code knows anything about
networking. The system takes care of it for you (mostly thanks to
9p, as sqweek described).
In terms of concurrency, that's more of a programming question
than an OS question (which isn't to say the OS isn't relevant).
Plan 9's thread(2) library is probably the most relevant thing
there. It follows a very different (and easier to learn, read, and
write) model than the threads you see in other systems. Plan
9 mostly helps there by making...
Show full article (0.96Kb)
no comments
Re: [9fans] Plan 9 and multicores/parallelism/concurrency?         


Author: David Leimbach
Date: Jul 14, 2008 08:37

On Mon, Jul 14, 2008 at 1:45 AM, ssecorp 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...
Show full article (2.74Kb)
1 Comment
Re: [9fans] Plan 9 and multicores/parallelism/concurrency?         


Author: erik quanstrom
Date: Jul 14, 2008 09:14

> 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.

due to the specific meaning of "thread" in the thread
library, this statement is misleading.

only procs may run in parallel. threads are scheduled
cooperatively. since procs are scheduled by the kernel,
the kernel is responsible for scheduling procs; the thread
library doesn't grab processors.

- erik
no comments
Re: [9fans] Plan 9 and multicores/parallelism/concurrency?         


Author: Iruata Souza
Date: Jul 14, 2008 09:22

On 7/14/08, sqweek gmail.com> wrote:
> On Mon, Jul 14, 2008 at 4:45 PM, ssecorp 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.
>>
>
>> In what way does it make it easy?
>
>
> Plan 9 makes it easy via 9p, its file system/resource sharing
> protocol. In plan 9, things like graphics and network drivers export a
> 9p interface (a filetree). Furthermore, 9p is network transparent
> which means accesses to remote resources look exactly like accesses to
> local resources, and this is the main trick - processes do not care
> whether the file they are interested in is being served by the kernel,
> a userspace process, or a machine half way across the world.
> ...
Show full article (0.90Kb)
no comments
Re: [9fans] Plan 9 and multicores/parallelism/concurrency?         


Author: Roman V. Shaposhnik
Date: Jul 14, 2008 09:32

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.
Show full article (1.20Kb)
no comments
Re: [9fans] Plan 9 and multicores/parallelism/concurrency?         


Author: Roman V. Shaposhnik
Date: Jul 14, 2008 09:33

On Mon, 2008-07-14 at 17:08 +0800, sqweek wrote:
> On Mon, Jul 14, 2008 at 4:45 PM, ssecorp 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.
>>
>> In what way does it make it easy?
>
> Plan 9 makes it easy via 9p, its file system/resource sharing
> protocol. In plan 9, things like graphics and network drivers export a
> 9p interface (a filetree). Furthermore, 9p is network transparent
> which means accesses to remote resources look exactly like accesses to
> local resources, and this is the main trick - processes do not care
> whether the file they are interested in is being served by the kernel,
> a userspace process, or...
Show full article (1.03Kb)
no comments