The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: ron@ronnatalie.com (Ron Natalie)
Subject: [TUHS] Unix with TCP/IP for small PDP-11s
Date: Sun, 21 May 2017 07:04:02 -0400	[thread overview]
Message-ID: <020201d2d221$f55e08e0$e01a1aa0$@ronnatalie.com> (raw)
In-Reply-To: <1495343623.794127.983422680.4D5F43AD@webmail.messagingengine.com>

> Also, x86 is totally "split I/D" by any relevant definition, and has a 20-bit physical address space.

The physical address space isn't the issue.    The PDP-11's (well the later ones) had 22 bits of address space.

Even the amount of virtual address space wasn't the problem.   The problem was really the lack of segments    The PDP11, only had 8 for code and 8 for the combined stack/data (on the split I/D) machine.
While we were able to "thunk" in a code overlay system without any real hardware support, there's no way to do that practically for data.

As I stated earlier, using the BSD networking code, we ran out of the combined code/data registers when it came to having ot have one to map the mbufs.   I supposed you could have added more magic (and perhaps th is is what the later Ultrix did), to carefully unmap one of the data segements to get to the network data, but boy, we never figured out a good way to do that when we tried.    We retired all but the 11/70's (which we had three of) at the time as the Vaxes and other machines were beginning to roll in.    In fact, I did eventually also turn one of the 11/70's into a router using my LOS (little operating system...no time for sharing, uniprocessor system) gateway OS.    Each driver ran in it's own little program so it was a lot easier.




  reply	other threads:[~2017-05-21 11:04 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1.1495245601.20449.tuhs@minnie.tuhs.org>
2017-05-20 10:46 ` Johnny Billquist
2017-05-20 17:39   ` Henry Bent
2017-05-20 20:40     ` Johnny Billquist
2017-05-20 20:44       ` Henry Bent
2017-05-20 18:18   ` Warner Losh
2017-05-20 19:05     ` arnold
2017-05-20 20:29       ` Warner Losh
2017-05-20 21:41       ` David Arnold
2017-05-20 21:59         ` Erik E. Fair
2017-05-20 20:40     ` Johnny Billquist
2017-05-20 21:05       ` Warner Losh
2017-05-20 21:34         ` Johnny Billquist
2017-05-21  5:13           ` Random832
2017-05-21 11:04             ` Ron Natalie [this message]
2017-05-24 15:21 Noel Chiappa
2017-05-24 17:19 ` Jeremy C. Reed
     [not found] <mailman.1.1495591202.25149.tuhs@minnie.tuhs.org>
2017-05-24  9:20 ` Paul Ruizendaal
  -- strict thread matches above, loose matches on Subject: below --
2017-05-23 13:43 Noel Chiappa
2017-05-23 11:35 Paul Ruizendaal
2017-05-23  1:33 Noel Chiappa
2017-05-23  1:14 Noel Chiappa
2017-05-22  9:28 Paul Ruizendaal
2017-05-22 14:09 ` Clem Cole
2017-05-22 14:51   ` Steve Simon
2017-05-22 16:29     ` Clem Cole
2017-05-22 16:35       ` Ron Natalie
2017-05-22 22:07       ` Paul Ruizendaal
2017-05-22 23:25         ` Clem Cole
2017-05-23  0:36           ` Paul Ruizendaal
2017-05-19 15:15 Noel Chiappa
2017-05-19 16:29 ` Henry Bent
2017-05-19 19:04   ` Ron Natalie
2017-05-20  0:15     ` Warner Losh
2017-05-20  0:21       ` Warner Losh
2017-05-19 17:39 ` Clem Cole
2017-05-21 16:16   ` Dave Horsfall
2017-05-21 19:58     ` Clem Cole
2017-05-21 20:57       ` Ron Natalie
2017-05-21 21:26         ` Clem Cole
2017-05-21 21:46         ` William Pechter

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='020201d2d221$f55e08e0$e01a1aa0$@ronnatalie.com' \
    --to=ron@ronnatalie.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).