From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Got thread experience?
Date: Thu, 25 Oct 2007 22:28:59 +0100 [thread overview]
Message-ID: <3a2427bcd4288f678b00408a03f4b282@terzarima.net> (raw)
In-Reply-To: <47210127.8080107@gmail.com>
> 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).
next prev parent reply other threads:[~2007-10-25 21:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 20:48 don bailey
2007-10-25 20:51 ` erik quanstrom
2007-10-25 21:01 ` don bailey
2007-10-25 21:06 ` erik quanstrom
2007-10-25 21:13 ` don bailey
2007-10-25 21:17 ` erik quanstrom
2007-10-25 21:17 ` Pietro Gagliardi
2007-10-25 21:05 ` Pietro Gagliardi
2007-10-25 21:12 ` don bailey
2007-10-25 21:28 ` Charles Forsyth [this message]
2007-10-25 21:44 ` roger peppe
2007-10-25 23:30 ` Andy Newman
2007-10-26 15:30 ` don bailey
2007-10-25 22:12 ` David Leimbach
2007-10-25 21:35 ` Sape Mullender
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=3a2427bcd4288f678b00408a03f4b282@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.edu \
/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).