From: Jon Steinhart <jon@fourwinds.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] non-blocking IO - threads
Date: Tue, 02 Jun 2020 15:03:58 -0700 [thread overview]
Message-ID: <202006022203.052M3wpa167150@darkstar.fourwinds.com> (raw)
In-Reply-To: <515ABF82-79D4-4DB8-90F1-4DDD512C7706@serissa.com>
Lawrence Stewart writes:
> I’ve always thought select(2) was a pretty good thing. In 1995 at Open
> Market we had a single-process web server that had no difficulties
> running 1000 to 1200 connections. I think that was BSD, and later OSF-1.
So select was a great thing until interactive graphics came along. Just
got too messy. I recall writing assembly language code to support threads
in the mid to late 1980s, and I remember reading some papers from Sun about
the same. Everybody was doing it. Anybody have enough of the history to
paint a picture of how we got from there to standardized threads?
Jon
next prev parent reply other threads:[~2020-06-02 22:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-02 14:19 [TUHS] non-blocking IO Paul Ruizendaal
2020-06-02 17:45 ` Paul Winalski
2020-06-02 17:59 ` arnold
2020-06-02 18:53 ` Paul Winalski
2020-06-02 19:18 ` Clem Cole
2020-06-02 21:15 ` Lawrence Stewart
2020-06-02 22:03 ` Jon Steinhart [this message]
2020-06-02 23:05 ` [TUHS] non-blocking IO - threads Rob Pike
2020-06-02 23:09 ` Rob Pike
2020-06-02 23:21 ` Larry McVoy
2020-06-03 0:39 ` Rob Pike
2020-06-02 23:12 ` Jon Steinhart
2020-06-03 16:42 ` Paul Winalski
2020-06-03 17:57 ` Jon Forrest
2020-06-03 5:38 ` [TUHS] Unix on the Arpanet Lars Brinkhoff
2020-06-03 12:23 ` Lawrence Stewart
2020-06-02 18:23 ` [TUHS] non-blocking IO Dan Cross
2020-06-02 18:56 ` Paul Winalski
2020-06-02 19:23 ` Clem Cole
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=202006022203.052M3wpa167150@darkstar.fourwinds.com \
--to=jon@fourwinds.com \
--cc=tuhs@minnie.tuhs.org \
/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).