From: Wesley Felter <wesf@cs.utexas.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Any significant gotchas?
Date: Fri, 14 Jul 2000 09:20:20 +0000 [thread overview]
Message-ID: <B593FDF2.CBBA%wesf@cs.utexas.edu> (raw)
In-Reply-To: <200007121455.KAA01408@egyptian-gods.mit.edu>
in article 200007121455.KAA01408@egyptian-gods.mit.edu, Greg Hudson at
ghudson@mit.edu wrote on 7/12/00 10:13 AM:
>> Maybe Plan 9 can do this cleaner, maybe not, the trick is it is a
>> very mutable system that isn't UNIX and offers you the opportunity
>> to look at things in a different way.
>
> Just to relay one such idea, I'm told Solaris has introduced a
> /dev/poll in recent versions. (Though it doesn't happen to be in
> Solaris 7, the most recent version I have access to at the moment.)
> The idea seems fairly straightforward and should scale quite well.
The Linux Scalability Project has /dev/poll patches for Linux and a paper
comparing poll(), /dev/poll, and queued realtime signals (which are really
more like event queues than signals IMO).
http://www.citi.umich.edu/projects/linux-scalability/index.html
The ScalaServer project proposed another event queue API, which may be
similar to the one recently adopted in FreeBSD.
http://www.cs.rice.edu/CS/Systems/ScalaServer/index.html
SGI has a very lightweight threads library, although I'm skeptical that it
can beat the event-driven model.
http://oss.sgi.com/projects/state-threads/
Wesley Felter - wesf@cs.utexas.edu
next prev parent reply other threads:[~2000-07-14 9:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 14:43 jmk
2000-07-12 14:55 ` Greg Hudson
2000-07-14 9:20 ` Wesley Felter [this message]
2000-07-14 14:55 ` Douglas A. Gwyn
2000-07-12 16:36 ` John S. Dyson
[not found] <10007111441.ZM757223@marvin>
2000-07-12 13:39 ` Stephen C. Harris
[not found] <sharris@sch1.NCTR.FDA.GOV>
2000-07-11 21:10 ` Stephen C. Harris
2000-07-11 21:20 ` Scott Schwartz
2000-07-12 9:31 ` Jason Ozolins
2000-07-12 12:08 ` John S. Dyson
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=B593FDF2.CBBA%wesf@cs.utexas.edu \
--to=wesf@cs.utexas.edu \
--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).