The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
To: tuhs@minnie.tuhs.org
Cc: jnc@mercury.lcs.mit.edu
Subject: Re: [TUHS] Memory on Lion's v6
Date: Mon, 28 Feb 2022 19:44:22 -0500 (EST)	[thread overview]
Message-ID: <20220301004422.EB7A118C07B@mercury.lcs.mit.edu> (raw)

    > From: Will Senn

    > 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:
    > ..
    > ; PDP11/40 processor;
    > ...
    > It seems like he must have had an MMU

V6 absolutely requires an MMU; the need for it is all throughout basic
attributes of the system - e.g. user processes start their address space at 0.

(BTW, there are V6 descendants, MINI-UNIX:

  http://gunkies.org/wiki/MINI-UNIX

and LSX, which don't use/need an MMU, and run on -11 models without memory
managament, such as -11/05's, but I don't think they were in wide use outside
Bell.)


    > and 128k memory

The -11/40, as originally released, only supported the MM11-L, which came in
multiples of 16KB (for a 3-board set). Use of the later MM11-U (32KB units)
required a new main power harness, which only came in on
higher-serial-numbered -11/40's.

The -11/40 (as it was at first) that I had at LCS had, to start with, I'm
pretty sure, 3 MM11-L units (i.e. one MM11-L backplane full) - i.e. 48KB. I
know this sounds incredible, and I'm having a hard time believing it myself,
wondering if my memory is failing with age; but it definitely had
extraordinarily little.

I just looked on my V6 (running in a simulator), and it appears that by
trimming all parameters (e.g. number of disk buffers) to the absolute bone,
the kernel could be trimmed to about 36KB. (I haven't actually tried it,
since I don't feel like recompiling all the kernel modules, but one can
estimate it - take the current system size [44KB], delete 10 buffers @ .5KB
gives 39KB, etc, etc.)

That would allow a maximum user process of 12KB on a 48KB machine - and
MINI-UNIX, which runs basically stock V6 user code, can manage with user
processes that small.

I see Andrew's email which reports that the Lions machine had more main
memory, 128KB (maybe 4 MM11-U's - two MM11-U backplanes full); that 
woould have made their life a lot easier.

	Noel

             reply	other threads:[~2022-03-01  0:48 UTC|newest]

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

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=20220301004422.EB7A118C07B@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).