From: Tony Finch <dot@dotat.at>
To: joe mcguckin <joe@via.net>
Cc: TUHS main list <tuhs@minnie.tuhs.org>, Paul Ruizendaal <pnr@planet.nl>
Subject: Re: [TUHS] STREAMS performance
Date: Tue, 14 Apr 2020 15:54:23 +0100 [thread overview]
Message-ID: <alpine.DEB.2.20.2004141543200.26709@grey.csi.cam.ac.uk> (raw)
In-Reply-To: <37F9655C-D42C-4504-9926-129F6DF5C158@via.net>
[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]
joe mcguckin <joe@via.net> wrote:
>
> I seem to remember that Sun was trying to sell boxes to the airline /
> reservation industry, and one of the ways they came up with to make
> Solaris handle thousands of ascii terminals was to push the character
> discipline code into streams in order to eliminate the multiple
> user/kernel crossings per character being handled…
I encountered this feature when deploying some new Solaris 2.5.1 / 2.6 web
servers in about 1997/8. We were chroot()ing the user login daemons
(telnet and ftp) to improve security, and they wouldn't work on a freshly
rebooted server. Eventually I worked out that telnetd loaded a kernel
module on demand, and this didn't work when it was chroot()ed, but telnetd
could skip it if the module had previously been loaded. (I could see from
truss and/or strings that telnetd was specifying an absolute path to the
module rather than expecting the kernel to know where to find it.) I was
kind of impressed by the performance engineering, and it stuck in my
memory because it took me so long to understand why it sometimes didn't
work...
Tony.
--
f.anthony.n.finch <dot@dotat.at> http://dotat.at/
Trafalgar: Variable 3 or 4 at first in southeast, otherwise cyclonic 5 to 7.
Moderate or rough, occasionally very rough at first in northwest. Rain or
thundery showers. Good, occasionally poor.
next prev parent reply other threads:[~2020-04-14 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 10:03 Paul Ruizendaal
2020-04-12 22:55 ` joe mcguckin
2020-04-14 14:54 ` Tony Finch [this message]
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=alpine.DEB.2.20.2004141543200.26709@grey.csi.cam.ac.uk \
--to=dot@dotat.at \
--cc=joe@via.net \
--cc=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).