> So, those with experience with threading implementations on weird
> real-time or embedded operating systems:
>
> Have you ever ran into a thread implementation where two threads
> could *not* directly access each other's .bss (or equiv)/heap?
>
> i.e. have you ever encountered a scenario where sibling threads
> actually had completely separate sets of page tables?
Plan 9 distinguishes between threads and procs. Procs are Plan 9
processes and can therefore have address spaces different from other
processes. Usually, in threaded applications, the proc address
spaces only differ in the stack.
However, we have real-time embedded applications where some procs
map in memory segments that can be used to access certain peripherals.
In such applications procs do have different address spaces. But they
are only somewhat different, certainly not as different as indicated
above.
sape
