From: Sergey Reva <rs_rlab@mail.ru>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] How it work?
Date: Wed, 23 Mar 2005 08:57:56 +0200 [thread overview]
Message-ID: <538092562.20050323085756@mail.ru> (raw)
In-Reply-To: <Pine.BSI.4.61.0503221431500.25349@malasada.lava.net>
Hello fans
Thanks Tim for advice!
Now I find:
1. "lock" used tas (test-and-set), in libc too
2. "queuing lock" use "lock", and also suspend task which wait locking
3. "rendezvous" can handle two task (and live in kernel)
4. "Rendez" (as subset of rsleep;rwakeup;rwakeupall) can handle multiple
tasks (and live in libc)
Is it right?
TN> There are several types of locks. Some (like spin locks) can operate
TN> without any assistance from the kernel (not entirely, they yield with a
TN> syscall). Others (like rendezvous) use the kernel to mediate between the
TN> processes.
As I seen both rendezvous and Rendez(rsleep;rwakeup;rwakeupall)
change state of process but Rendez can do this even in libc, where is
different other than state of process: Rendezvous (in syscall) and
Sleep (in rendez)? why rendezvous need to be at kernel?
--
http://rs-rlab.narod.ru mailto:rs_rlab@mail.ru
next prev parent reply other threads:[~2005-03-23 6:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-22 19:00 Sergey Reva
2005-03-23 0:40 ` Tim Newsham
2005-03-23 6:57 ` Sergey Reva [this message]
2005-03-23 17:34 ` Russ Cox
2005-03-24 8:46 ` Sergey Reva
2005-03-24 8:55 ` noselasd
[not found] ` <4439b95e268ad4987f174271ac554f28@smtp.songnetworks.no>
2005-03-25 10:33 ` Sergey Reva
2005-03-25 17:08 ` Russ Cox
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=538092562.20050323085756@mail.ru \
--to=rs_rlab@mail.ru \
--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).