From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] vfork and paging
Date: Tue, 2 Oct 2001 16:39:17 +0100 [thread overview]
Message-ID: <20011002152706.3B01419A34@mail.cse.psu.edu> (raw)
> It is indeed true that you have to know what your program does. With
> the thread library by default you share memory and fd's so accessibility
> doesn't change twixt light and heavy threads, though syncronization problems
> will be more likely to rear their ugly heads in the latter.
i was finding it difficult to debug rio, possibly because it has a
good mix of procs and threads and working out which function is being
called from what isn't too easy...
> I wrote ndb/cs and ndb/dns before the thread library and it was a bit
> of a pain. I'le like to redo dns with it.
if i ever have to do multi-threaded code in C on another platform
again i shall port and use the plan 9 thread library - it's by far the
most reasonable i've seen.
i would miss the type checking on channels though.
i used to use occam, which had channels, but you could only use them
completely statically (no dynamic memory, no recursion, etc); the
possibilities afforded by dynamic channels are wonderful...; they make
some things so simple to implement.
rog.
next reply other threads:[~2001-10-02 15:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 15:39 rog [this message]
2001-10-03 7:38 ` Boyd Roberts
-- strict thread matches above, loose matches on Subject: below --
2001-10-19 21:03 David Gordon Hogan
2001-10-04 16:29 forsyth
2001-10-04 14:09 rog
2001-10-04 10:17 Richard Miller
2001-10-03 10:16 rog
2001-10-03 10:31 ` Boyd Roberts
2001-10-03 9:49 forsyth
2001-10-03 10:52 ` Boyd Roberts
2001-10-03 13:55 ` Borja Marcos
2001-10-03 14:23 ` Ronald G Minnich
2001-10-02 21:05 forsyth
2001-10-02 19:25 rob pike
2001-10-02 18:51 rog
2001-10-02 18:05 Russ Cox
2001-10-02 15:56 rob pike
2001-10-02 15:27 Fco.J.Ballesteros
2001-10-02 14:37 Sape Mullender
2001-10-02 14:31 rog
2001-10-02 14:29 presotto
2001-10-02 14:12 rog
2001-10-02 13:48 Sape Mullender
2001-10-02 13:47 rob pike
2001-10-02 13:42 Sape Mullender
2001-10-01 14:06 rob pike
2001-10-01 15:42 ` Douglas A. Gwyn
2001-10-01 14:01 forsyth
2001-10-01 12:21 rob pike
2001-10-02 8:27 ` Boyd Roberts
2001-10-02 13:34 ` Ronald G Minnich
2001-10-01 10:45 forsyth
2001-10-01 10:59 ` Boyd Roberts
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=20011002152706.3B01419A34@mail.cse.psu.edu \
--to=rog@vitanuova.com \
--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).