From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] screen editors / machine load
Date: Fri, 10 Jan 2020 09:35:39 -0500 (EST) [thread overview]
Message-ID: <20200110143539.94B6218C09C@mercury.lcs.mit.edu> (raw)
> From: Otto Moerbeek <otto@drijf.net>
> I believe it was not only vi itself that was causing the load, it was
> also running many terminals in raw mode that killed performance.
I'm not familiar with the tty driver in late versions of Unix like 4.1 (sic),
but I'm very familiar with the one in V6, and it's not the raw mode _itself_
that caused the load (the code paths in the kernel for cooked and raw aren't
that different), but rather the need to wake up and run a process on every
character that was the real load.
When Bernie Greenberg did EMACS for Multics, he had a similar issue. I recall
reading a document with an extensive discussion of how they dealt with this,
especially when using the system over the ARPANET. IIRC, normal printing
characters were echoed without waking up the process; remotely, when using
the network. If anyone's really interested in this, and can't find it themselves,
I can try looking for it.
Noel
next reply other threads:[~2020-01-10 14:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 14:35 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-10 15:35 Noel Chiappa
2020-01-08 7:39 [TUHS] screen editors Thomas Paulsen
2020-01-08 21:49 ` Dave Horsfall
2020-01-10 8:13 ` markus schnalke
2020-01-10 13:41 ` [TUHS] screen editors / machine load Mike Markowski
2020-01-10 13:56 ` Otto Moerbeek
2020-01-10 15:00 ` Mary Ann Horton
2020-01-10 15:48 ` Clem Cole
2020-01-10 22:18 ` Adam Thornton
2020-01-11 0:30 ` Christopher Browne
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=20200110143539.94B6218C09C@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.edu \
--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).