9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: palazzol@comcast.net
To: 9fans@9fans.net
Subject: [9fans] Threading Model Questions
Date: Tue, 20 May 2008 14:10:38 +0000	[thread overview]
Message-ID: <052020081410.8330.4832DBDE0001F9A00000208A2206998499040196960E040E9F@comcast.net> (raw)


Hello,

I've been looking into the Bell Labs CSP-style threading model, trying a few test programs, and watching the Russ Cox and Rob Pike movies.  I have a few of questions.

1) Are there any valid criticisms to this approach?  Everyone seems to agree it is superior to "lower-level" models, but are there any areas where this model doesn't work comparatively well?

2) Are there examples of the equivalence between this model and other ones (in terms of capability)

3) Why are the existing CSP-based libraries for other OS's (C++CSP2, JCSP, pyCSP) much more complex?  It seems like passing "channel ends" instead of channels might be a good idea, but the rest of the stuff seems like complexity with limited/no benefit?  For example, defining channels as One2One, One2Any, etc.  Also, the idea of scoped forking versus "free-form" thread/process creation.

4) Finally, it looks like libthread has support for a lot of non-CSP stuff.  Is this part used much?  Or is it just there for historical and/or completeness reasons.

Thanks for any opinions!
-Frank



             reply	other threads:[~2008-05-20 14:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20 14:10 palazzol [this message]
2008-05-20 18:50 ` erik quanstrom
2008-05-21  0:37 ` Russ Cox
2008-05-28  5:36   ` Frank Palazzolo
2008-05-20 21:21 palazzol

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=052020081410.8330.4832DBDE0001F9A00000208A2206998499040196960E040E9F@comcast.net \
    --to=palazzol@comcast.net \
    --cc=9fans@9fans.net \
    /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).