From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Channels and threads
Date: Wed, 7 Nov 2007 18:39:49 -0500 [thread overview]
Message-ID: <3687635846c800c4ec129e333b0c3f35@quanstro.net> (raw)
In-Reply-To: <509071940711071525t6459cf1ch3ea12c91ad48787c@mail.gmail.com>
> On 11/7/07, erik quanstrom <quanstro@quanstro.net> wrote:
>
> // wiring data to processors would make more sense.
>
> is what's meant here "wiring (data+proc) to processors would make more sense"?
no, if you're using threads (procs), by definition mutiple actors are
chewing on the same data. if performance matters enough to worry
about which processor does what, i would think your data set would be
large enough to be much bigger than the active code. therefore, i
would worry about keeping the data set wired to a processor and not
worry about which procs are running where.
- erik
next prev parent reply other threads:[~2007-11-07 23:39 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
2007-11-07 22:41 ` don bailey
2007-11-07 23:25 ` Anthony Sorace
2007-11-07 23:39 ` erik quanstrom [this message]
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=3687635846c800c4ec129e333b0c3f35@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).