From: Larry McVoy <lm@mcvoy.com>
To: Norman Wilson <norman@oclsc.org>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] V8, V9 and V10 now in the "Unix Tree"
Date: Sat, 11 Apr 2020 08:44:28 -0700 [thread overview]
Message-ID: <20200411154428.GF10016@mcvoy.com> (raw)
In-Reply-To: <20200411153844.910A04422F@lignose.oclsc.org>
On Sat, Apr 11, 2020 at 11:38:44AM -0400, Norman Wilson wrote:
> -- Stream I/O system added; all communication-device
> drivers (serial ports, Ethernet, Datakit) changed to
> work with streams. Pipes were streams.
How was performance? Was this Dennis' streams, not Sys V STREAMS?
I ported Lachmans/Convergents STREAMS based TCP/IP stack to the
ETA 10 Unix and SCO Unix and performance just sucked. Ditto for
the Solaris port (which I did not do, I don't think it made any
difference who did the port though).
next prev parent reply other threads:[~2020-04-11 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-11 15:38 Norman Wilson
2020-04-11 15:44 ` Larry McVoy [this message]
2020-04-11 18:52 ` arnold
-- strict thread matches above, loose matches on Subject: below --
2020-04-12 9:30 Paul Ruizendaal
2020-04-12 10:00 ` Rob Pike
2020-04-12 9:26 Paul Ruizendaal
2020-04-11 15:24 Norman Wilson
2020-04-11 18:49 ` arnold
2020-04-11 14:47 Doug McIlroy
2020-04-10 15:34 Paul Ruizendaal
2020-04-10 20:50 ` Rob Pike
2020-04-12 8:51 ` Paul Ruizendaal
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=20200411154428.GF10016@mcvoy.com \
--to=lm@mcvoy.com \
--cc=norman@oclsc.org \
--cc=tuhs@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).