The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: (Noel Chiappa)
Subject: Re: [TUHS] Unix for PDP11/20 w/o mmu or paging option
Date: Fri, 17 Sep 2021 16:18:47 -0400 (EDT)	[thread overview]
Message-ID: <> (raw)

    > From: Clem Cole

    > The KS11 MMU for the 11/20 was built by CSS ... I think Noel has done
    > more investigation than I have.

I got a very rough description of how it worked, but that was about it.

    > I'm not sure if the KS11 code is still there. I did not think so.

No, the KS11 was long gone by later Vn. Also,I think not all of the -11/20
UNIX machines had it, just some.

    > The V1 work was for a PDP-7

Actually, there is a PDP-11 version prior to V2, canonically called V1.
The PDP-7 version seems to be called 'PDP-7 UNIX' or 'V0'.

    > I'm fairly sure that the RK05,  used the RK11-D controller.

Normally, yes. I have the impression that one could finagle RK03's to work on
the RK11-D, and vice versa for RK05's on the RK11-C, but I don't recall the
details. The main difference between the RK11-C and -D (other then the
implementation) was that i) the RK11-C used one line per drive for drive
selection (the -D used binary encoding on 3 lines), and ii) it had the
'maintenance' capability and register (al omitted from the -D).

    > The difference seems to have been in drive performance.

Yes, but it wasn't major. They both did 1500RPM, so since they used
the same pack format, the rotational delay, transfer rate, etc were
identical. The one peformance difference was in seeks; the
average on the RK01 was quoted as 70 msec, and 50 msec on the

    > Love to see the {KT11-B prints] and if you know where you found them.

They were sold on eBait along with an -11/20 that allegedly had a KT11-B. (It
didn't; it was an RK11-C.) I managed to get them scanned, and they and the
minimal manual are now in Bitsavers. I started working on a Tech Manual for
it, but gave up with it about half-way done.

    > I wonder if [our V1 source] had the KS-11 stuff in it. 

No; I had that idea a while back, looked carefully, our V1 listings
pre-date the KS11.

    > From: Roland Huisman

    > There is a KT11B paging option that makes the PDP11/20 a 18 bit
    > machine.

Well, it allows 2^18 bytes of main memory, but the address space of the
CPU is still2^16 bytes.

    > It looks a bit like the TC11 DECtape controller.

IITC, it's two backplanes high, the TC11 is one. So more like the RK11-C...

    > I have no idea how it compares to the later MMU units from the
    > software perspective.

Totally different; it's real paging (with page tables stored in masin
memory). The KT11-B provides up to 128 pages of 512 bytes each, in both Exec
and User mode. The KT11-C, -D etc are all segmentation, with all the info
stored in registers in the unit.

    > I wonder is there is some compatibility with the KT11-B [from the KS11]

I got the impression that the KS11 was more a 'base and bounds' kind
of thing.


             reply	other threads:[~2021-09-17 20:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17 20:18 Noel Chiappa [this message]
2021-09-17 20:47 ` Clem Cole
  -- strict thread matches above, loose matches on Subject: below --
2021-09-17 15:35 Noel Chiappa
2021-09-17 18:28 ` Phil Budne
2021-09-17 19:43   ` Clem Cole
2021-09-17 19:51     ` Brantley Coile
2021-09-17 20:07       ` Clem Cole
2021-09-17 21:21       ` Phil Budne
     [not found] <>
2021-09-17 14:09 ` Roland via TUHS
2021-09-17 14:33   ` Warner Losh
2021-09-17 15:32     ` Clem Cole
2021-09-17 16:04       ` Roland via TUHS
2021-09-17 16:14         ` Clem Cole
2021-09-17 16:44           ` Roland via TUHS
2021-09-17 16:13       ` Warner Losh
2021-09-17 16:17         ` Clem Cole
2021-09-17 16:05     ` Roland via TUHS

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* 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).