From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <3e1162e60710251512q11e31590j4bd0071d9f119e0e@mail.gmail.com> Date: Thu, 25 Oct 2007 15:12:17 -0700 From: "David Leimbach" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] Got thread experience? In-Reply-To: <3a2427bcd4288f678b00408a03f4b282@terzarima.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_2263_21766260.1193350337785" References: <47210127.8080107@gmail.com> <3a2427bcd4288f678b00408a03f4b282@terzarima.net> Topicbox-Message-UUID: da1bbb96-ead2-11e9-9d60-3106f5b1d025 ------=_Part_2263_21766260.1193350337785 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 10/25/07, Charles Forsyth wrote: > > > 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? > > yes. erlang processes do not share memory (and it is used in embedded > real-time applications). > > > Aren't those processes though and not threads? ------=_Part_2263_21766260.1193350337785 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

On 10/25/07, Charles Forsyth <forsyth@terzarima.net> wrote:
> 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?

yes. erlang processes do not share memory (and it is used in embedded real-time applications).


Aren't those processes though and not threads? ------=_Part_2263_21766260.1193350337785--