From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Channels and threads
Date: Wed, 7 Nov 2007 16:55:47 -0500 [thread overview]
Message-ID: <13edbccfbea367d2454018035c47ad0c@quanstro.net> (raw)
In-Reply-To: <47322FE4.2060107@gmail.com>
> So, what's the rationale behind using Channels?
> Is passing by reference not recommended by Plan 9 design?
>
> D
channels (the libthread variety) may pass by reference or value.
so passing by reference or value is orthagonal to the question
of why channels.
for example, if you have a couple of i/o threads and one mux,
the mux can wait for a message from one of the i/o threads
that might say
a) here's your data (8192 byte+overhead message), or
b) your data is here (sizeof pointer+overhead message)
- erik
next prev parent reply other threads:[~2007-11-07 21:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-07 21:36 don bailey
2007-11-07 21:55 ` erik quanstrom [this message]
2007-11-07 22:02 ` don bailey
2007-11-07 22:12 ` erik quanstrom
2007-11-07 22:41 ` don bailey
2007-11-07 23:25 ` Anthony Sorace
2007-11-07 23:39 ` erik quanstrom
2007-11-07 22:24 ` david jeannot
2007-11-07 22:17 ` ron minnich
2007-11-07 22:35 ` don bailey
2007-11-11 7:18 ` Navin Johnson
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=13edbccfbea367d2454018035c47ad0c@quanstro.net \
--to=quanstro@quanstro.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).