From: Paul Ruizendaal <pnr@planet.nl>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: [TUHS] STREAMS performance
Date: Sun, 12 Apr 2020 12:03:23 +0200 [thread overview]
Message-ID: <2DE6E671-7FD2-463A-B2E7-7951DBD15CA0@planet.nl> (raw)
> Date: Sat, 11 Apr 2020 08:44:28 -0700
> From: Larry McVoy
>
> 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?
It was streams, not 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).
STREAMS are outside the limited scope I try to restrain myself to, but I’m intrigued.
What in the above case drove/caused the poor performance?
There was a debate on the LKML in the late 1990’s where Caldera wanted STREAMS support in Linux and to the extent the arguments were technical *), my understanding of them is that the main show stopper was that STREAMS would make ‘zero copy’ networking impossible. If so, then it is a comment more about the underlying buffer strategy than STREAMS itself.
Did STREAMS also perform poorly in the 1986 context they were developed in?
Paul
*) Other arguments pro- and con included forward maintenance and market need, but I’m not so interested in those aspects of the debate.
next reply other threads:[~2020-04-12 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 10:03 Paul Ruizendaal [this message]
2020-04-12 22:55 ` joe mcguckin
2020-04-14 14:54 ` Tony Finch
2020-04-12 23:15 ` Anthony Martin
2020-04-13 1:43 ` Rob Pike
2020-04-13 3:00 ` Anthony Martin
2020-04-13 3:14 ` Rob Pike
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=2DE6E671-7FD2-463A-B2E7-7951DBD15CA0@planet.nl \
--to=pnr@planet.nl \
--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).