The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: milov@cs.uwlax.edu (Milo Velimirović)
Subject: [TUHS] pdp11 UNIX memory allocation. Was: termcap vs terminfo (was: I swear! I rtfm'ed)
Date: Tue, 6 Jan 2015 13:57:43 -0600	[thread overview]
Message-ID: <DBC71EB6-B41B-4257-A580-254C613D508E@cs.uwlax.edu> (raw)
In-Reply-To: <201501061222.t06CMvTO027313@freefriends.org>

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

Bringing a conversation back online.
On Jan 6, 2015, at 6:22 AM, arnold at skeeve.com wrote:

>> Peter Jeremy scripsit:
>>> But you pay for the size of $TERMCAP in every process you run.
> 
> John Cowan <cowan at mercury.ccil.org> wrote:
>> A single termcap line doesn't cost that much, less than a KB in most cases.
> 
> In 1981 terms, this has more weight. On a non-split I/D PDP-11 you only
> have 32KB to start with.  (The discussion a few weeks ago about cutting
> yacc down to size comes to mind…)

(Or even earlier than ’81.) How did pdp11 UNIXes handle per process memory? It’s suggested above that there was a 50-50 split of the 64KB address space between instructions and data. My own recollection is that you got any combination of instruction and data space that was <64KB. This would also be subject to limits of pdp11 memory management unit.

Anyone have a definitive answer or pointer to appropriate man page or source code?


Thanks,
Milo




  parent reply	other threads:[~2015-01-06 19:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.125.1420128672.3354.tuhs@minnie.tuhs.org>
2015-01-01 16:21 ` [TUHS] " Johnny Billquist
2015-01-01 17:04   ` Warner Losh
2015-01-02  1:50     ` Mary Ann Horton
2015-01-02 19:13       ` Erik E. Fair
2015-01-05  7:06         ` Peter Jeremy
2015-01-06  0:40           ` John Cowan
2015-01-06 12:22             ` arnold
2015-01-06 16:02               ` [TUHS] termcap vs terminfo Mary Ann Horton
2015-01-06 17:12                 ` arnold
2015-01-06 16:32               ` [TUHS] termcap vs terminfo (was: I swear! I rtfm'ed) Warner Losh
2015-01-06 19:57               ` Milo Velimirović [this message]
2015-01-06 20:01                 ` [TUHS] pdp11 UNIX memory allocation. Was: " Clem Cole
2015-01-02 20:12     ` [TUHS] " Steffen Nurpmeso

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=DBC71EB6-B41B-4257-A580-254C613D508E@cs.uwlax.edu \
    --to=milov@cs.uwlax.edu \
    /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).