From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Plan 9 and multicores/parallelism/concurrency?
Date: Mon, 14 Jul 2008 12:00:36 -0400 [thread overview]
Message-ID: <8802dc60a5367ce78284e2d2c431bade@quanstro.net> (raw)
In-Reply-To: <3e1162e60807140832u5df4ae00hae1ff467ef0b6b0b@mail.gmail.com>
> If libthread is able to grab real processors per thread and get them
> scheduled, one's concurrent style code ultimately ends up having potential
> to run in parallel on those cores/processors.
due to the specific meaning of "thread" in the thread
library, this statement is misleading.
only procs may run in parallel. threads are scheduled
cooperatively. since procs are scheduled by the kernel,
the kernel is responsible for scheduling procs; the thread
library doesn't grab processors.
- erik
next prev parent reply other threads:[~2008-07-14 16:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 8:45 ssecorp
2008-07-14 9:08 ` sqweek
2008-07-14 16:17 ` Iruata Souza
2008-07-14 16:31 ` Roman V. Shaposhnik
2008-07-14 10:15 ` a
2008-07-14 15:32 ` David Leimbach
2008-07-14 16:00 ` erik quanstrom [this message]
2008-07-14 16:29 ` Roman V. Shaposhnik
2008-07-14 20:08 ` a
2008-07-14 20:39 ` Roman V. Shaposhnik
2008-07-14 22:12 ` a
2008-07-17 12:26 ` Roman V. Shaposhnik
2008-07-17 12:40 ` erik quanstrom
2008-07-17 13:00 ` ron minnich
2008-07-14 20:43 ` Charles Forsyth
2008-07-14 16:35 erik quanstrom
[not found] <f1209aefaab5eece7465c3d0df545ddd@quanstro.net>
2008-07-14 20:33 ` Roman V. Shaposhnik
2008-07-15 1:37 ` Joel C. Salomon
2008-07-15 8:01 ` Bakul Shah
2008-07-15 17:50 ` Paul Lalonde
2008-07-17 19:29 ` Bakul Shah
2008-07-18 3:31 ` Paul Lalonde
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=8802dc60a5367ce78284e2d2c431bade@quanstro.net \
--to=quanstro@quanstro.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).