The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] PDP-11 MMU (was: 68000 vs. 8086)
Date: Thu, 30 Jun 2016 20:01:01 -0400	[thread overview]
Message-ID: <CAC20D2PsCGf-+4yzai5sBbKhpxsvVn1=e-Uj8gEThRninwffPg@mail.gmail.com> (raw)
In-Reply-To: <e65515f8-137c-d149-a1a2-2a54f7ec9c72@update.uu.se>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2327 bytes --]

On Thu, Jun 30, 2016 at 6:17 PM, Johnny Billquist <bqt at update.uu.se> wrote:

> Clem, I think pretty much all you are writing is correct, except that I
> don't get your reference to the PDP-11 MMU.
>
> The MMU of the PDP-11 is not some base/limit register thing. It's a paged
> memory, with a flat address space. Admittedly, you only have 8 pages, but I
> think it's just plain incorrect to call it something else.
> (Even though noone I know of ever wrote a demand-paged memory system for a
> PDP-11, there is no technical reason preventing you from doing it. Just
> that with 8 pages, and load more physical memory than virtual, it just
> didn't give much of any benifits.)
>
​Johnny - yes I stand made more precise.   11's with MMU's do support
pages, but the MMU is is base/limits with 1 level page displacement and as
you point a not a lot of pages and with only 16 bits of base address the
virtual addresses are pretty limited (although as BSD 2.8 and later showed
you can do a lot with a bit of care and overlays).

I fairly certain that the original Moto MMU chip worked the same way, as
Nick and Les were definitely using the PDP-11/70 as the example, even
though those system did have more address bits.   I also, I know that the
custom MMU on the Magnolia the system we built at Tektronix with first
pre-68K did work that way, as I did it and I too model it from the 11/70.


In Magnolias case, it was that way because the Altos and Dorado's from PARC
did not have an MMU.   Roger Bates was my office mate at Tektronix and one
of the HW guys from the Dorado and Altos.  He was the main HW guy on
Magnolia had to learn about MMU's from me. But I was once a HW guy too --
and when we built that system those gates in Magnolia were mine :-)  The
original OS (Magix 1.0) ran PDP-11 style since that's all the CPU could do
(Magix was a V7 like system).   A couple of years later, when the CPU chips
were replaced with the first 68010's, the OS was updated to work more like
a Vax.   I've forgotten if Roger added a second level at that point, as I
had left the project to head back to grad school and I did not do that part
of the coding.

Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160630/760e6bdd/attachment-0001.html>


      reply	other threads:[~2016-07-01  0:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.31.1467314550.30583.tuhs@minnie.tuhs.org>
2016-06-30 22:17 ` Johnny Billquist
2016-07-01  0:01   ` Clem Cole [this message]

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='CAC20D2PsCGf-+4yzai5sBbKhpxsvVn1=e-Uj8gEThRninwffPg@mail.gmail.com' \
    --to=clemc@ccc.com \
    /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).