The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Memory on Lion's v6
Date: Mon, 28 Feb 2022 10:48:56 -0500	[thread overview]
Message-ID: <CAC20D2M90PZrD+n_+=vjjr3GFrpzGAd+Dacew-z2cFVceXNCTQ@mail.gmail.com> (raw)
In-Reply-To: <4e3c05d2-2496-b917-f1f4-1c6cba9ef58a@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2363 bytes --]

On Mon, Feb 28, 2022 at 12:51 AM Will Senn <will.senn@gmail.com> wrote:

> Does anybody know how much memory was configured on the PDP-11 that Lion's
> used for the commentary system. Here's what the book says about the system:
>
> ; from lions, page 1
> ; The code selection presumes a "model" system consisting of:
> ; PDP11/40 processor;
> ; RK05 disk drives;
> ; LP11 line printer;
> ; PC11 paper tape reader/punch;
> ; KL11 terminal interface.
>
> I usually add the mag tape, too
> ; TM10 magnetic tape - not in lions, but super handy
>
> It seems like he must have had an MMU and 128k memory, but I don't know.
> I'm hoping y'all remember, know, or can otherwise divine the correct value.
> I've run with no MMU - crash on boot. I've also run with less memory, but
> then cc won't build mkconf, when I have the TM10 enabled kernel loaded. As
> a reminder, his book was published in 1977.
>
> Thanks,
>
> Will
>

Can't tell you definitively.  You'd need to ask some one like Andrew.

FWIW: the 11/40 has a MMU, but does not support split I/D like the 45.  He
has  256K bytes [128k words] as the Max memory.  IIRC v6 will boot with 48K
words [96K bytes] - maybe a little less.  But the less physical memory, the
slower the system (the more it swaps).

DEC was just switching to semiconductor memory at the time and it was
pretty expensive.  The MS11-B was MOS based 18 bit x 4K word modules for
the 11/45, which were dual ported Unibus and Fastbus.  I have forgotten
what the 11/40 used as we tended not to use DEC memory modules***.

Lions and his team was likely to have been between 96K and 256K max,
depending on budget.    In my experience, we tended to build up to max
memory on systems, but only as soon as we could afford it.  In
my experience, we often bought the machines in phases... just enough to
boot it, with two or three RK05's to start.  Then add more memory and more
serial ports and more terminals.  Then more (larger) disk and maybe a tape
drive and printer, and then even more serial ports and some sort of modems
and network connections.


Clem



*** At CMU during those days, we tended to use aftermarket memory or
locally designed memory boards on the 11/40 and 11/34s as EE/CS had
negociate and bought a few megabytes of memory chips from National Semi for
C.mmp at a heavy discount - other groups could add to that order as needed.

[-- Attachment #2: Type: text/html, Size: 4235 bytes --]

  parent reply	other threads:[~2022-02-28 15:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28  5:48 Will Senn
2022-02-28  6:09 ` Warner Losh
2022-02-28 15:48 ` Clem Cole [this message]
2022-02-28 23:27   ` Andrew Hume
2022-03-01 15:31     ` Andrew Hume
2022-03-01  1:25 ` Bakul Shah
2022-03-01  0:44 Noel Chiappa
2022-03-02  1:19 Noel Chiappa
2022-03-02  2:15 ` Warner Losh
2022-03-02  2:26 Noel Chiappa

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='CAC20D2M90PZrD+n_+=vjjr3GFrpzGAd+Dacew-z2cFVceXNCTQ@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=tuhs@minnie.tuhs.org \
    --cc=will.senn@gmail.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).