From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Channels and threads
Date: Wed, 7 Nov 2007 17:12:39 -0500 [thread overview]
Message-ID: <a676fd6e3ce5686b1c34c183857eba69@quanstro.net> (raw)
In-Reply-To: <473235F0.80107@gmail.com>
> Well, yeah, I get that. I think the question I need to
> ask is "why use Channels at all?"
>
> What is the benefit of using Channels when threads can't
> be bound to a specific CPU in a multi-core system? Aren't
> Channels just a wrapper for locking a mutex and setting
> a variable or adding to a queue?
procs, not threads, can be "wired" to specific
processors. so if your interest is to wire tasks (for lack of a
better term) to processors, you can do that with procs.
on modern pc hardware, the gulf between memory and
the processor is large enough, that i'm not sure that you'd
want to wire procs to processors. wiring data to processors
would make more sense.
- erik
next prev parent reply other threads:[~2007-11-07 22:12 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
2007-11-07 22:02 ` don bailey
2007-11-07 22:12 ` erik quanstrom [this message]
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=a676fd6e3ce5686b1c34c183857eba69@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).