From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Solaris thread scheaduling
Date: Mon, 21 Aug 2000 08:59:17 +0000 [thread overview]
Message-ID: <399F22D5.66C37855@null.net> (raw)
In-Reply-To: <200008182054.QAA18235@cse.psu.edu>
> > Cooperative threads are just coroutines. They're `cooperative'
> > because if the thread doesn't cooperate by calling the scheduler,
> > no other thread ever get scheduled.
dhog@plan9.bell-labs.com wrote:
> It's a bit like, "cooperate -- or else!".
Well, if the tasks are decently coded, that can be a better
approach than preemptive scheduling where a task is interrupted
with things in an inconsistent state and all registers and status
flags have to be carefully preserved.
The operating systems in the Blit family of terminals used
cooperative scheduling.
next prev parent reply other threads:[~2000-08-21 8:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-18 20:53 dhog
2000-08-18 22:48 ` Boyd Roberts
2000-08-19 6:23 ` Lucio De Re
2000-08-21 8:59 ` Douglas A. Gwyn [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-08-21 16:34 dhog
2000-08-18 15:34 rob pike
[not found] ` <rob@plan9.bell-labs.com>
2000-08-18 20:25 ` Tom Duff
[not found] <slrn8pp28u.nsf.phil+s3@shell3.ba.best.com>
[not found] ` <slrn8pp4sr.iu9.dave@svarozic.srce.hr>
[not found] ` <399D2F7F.AD34496D@compaq.com>
2000-08-18 14:21 ` saroj
2000-08-18 14:53 ` kilgore
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=399F22D5.66C37855@null.net \
--to=dagwyn@null.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).