The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: dave@horsfall.org (Dave Horsfall)
Subject: [TUHS] Control-T (was top)
Date: Tue, 29 May 2018 11:12:09 +1000 (EST)	[thread overview]
Message-ID: <alpine.BSF.2.21.999.1805291057420.813@aneurin.horsfall.org> (raw)
In-Reply-To: <CABH=_VQ+R4svobbrcX12sL67qBN_+icViH8L=T+wx_csJ2KebA@mail.gmail.com>

On Mon, 28 May 2018, Paul Winalski wrote:

> DZ11s were available on PDP-11s and VAXen as well as the KS10. Because 
> the controller had no buffer it was dirt cheap.  OK, perhaps, for a 
> realtime or lab application, but if you were doing timesharing it could 
> bring the CPU to its knees in short order.  Some idiot decided to use 
> the same idea (no buffer in the controller) to reduce the cost of the 
> TU58 (aka DECtape II), Unlike the original DECtape, which was extremely 
> reliable, the TU58 was prone to frequent data overrun and underrun 
> errors even if you set things up such that it got top scheduler 
> priority.

Odd; I have a clear recollection that UNSW's driver (or was it Basser?) 
did not use interrupts (too slow, as you point out) but used the clock 
interrupt to empty the silos every so often.  I'd check the source in the 
Unix Archive, but I don't remember which disk image it's in; what I do 
remember was that it went like a bat out of hell, and Elec Eng had 
something like eight of them on their 11/70.

Can anyone confirm or deny this?

We also had a DZ-11 on our 11/60 (and the 11/40 before that), and it 
worked OK, keeping the DJ-11 company.

-- Dave, possibly suffering from mental bit-rot


  parent reply	other threads:[~2018-05-29  1:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-24 12:20 [TUHS] History of top Noel Chiappa
2018-05-24 14:09 ` Clem Cole
2018-05-24 14:43   ` Ronald Natalie
2018-05-24 14:50   ` [TUHS] Control-T (was top) Ronald Natalie
2018-05-24 15:01     ` Clem Cole
2018-05-24 15:48       ` Lars Brinkhoff
2018-05-24 15:08     ` Arthur Krewat
2018-05-28 22:32       ` Paul Winalski
2018-05-28 23:11         ` Clem cole
2018-05-28 23:32           ` Arthur Krewat
2018-05-29  1:12         ` Dave Horsfall [this message]
2018-05-28 10:31 ` [TUHS] History of top Lars Brinkhoff
2018-05-29  2:55 [TUHS] Control-T (was top) Noel Chiappa
2018-05-29 17:10 ` Paul Winalski
2018-05-29 18:49 Noel Chiappa
2018-05-30  1:05 ` Dave Horsfall
2018-05-29 21:21 Norman Wilson
2018-05-30  9:06 ` arnold
     [not found] <mailman.1.1527559201.18622.tuhs@minnie.tuhs.org>
2018-05-29 22:45 ` Johnny Billquist
2018-05-30  0:19   ` Clem cole
2018-05-30  0:20     ` Clem cole
2018-05-30 22:10     ` Johnny Billquist
2018-05-30 23:14       ` Pete Turnbull
2018-05-30  1:10   ` Dave Horsfall
     [not found] <mailman.1.1527732002.17884.tuhs@minnie.tuhs.org>
2018-05-31 15:02 ` Johnny Billquist
2018-05-31 21:42   ` Nemo

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.BSF.2.21.999.1805291057420.813@aneurin.horsfall.org \
    --to=dave@horsfall.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).