The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Unix with TCP/IP for small PDP-11s
Date: Mon, 22 May 2017 21:14:52 -0400 (EDT)	[thread overview]
Message-ID: <20170523011452.99DD518C095@mercury.lcs.mit.edu> (raw)

    > From: Paul Ruizendaal

    > There are two other routes to TCP/IP on a PDP11 without split I/D:
    > ...
    > DCEC's adaptation of the Wingfield TCP/IP library, designed to work
    > with V6. It is mostly a user space daemon, but requires some kernel
    > enhancements.

I wonder what the performance would be like, since the TCP is in a user
process (a different one from the application), i.e. there's a process switch
every time the application goes to send or receive data. This wouldn't have
been such an issue when the code was written, since ARPANet-type networks
were not very fast, but with a better network, it would have been limiting.


    > From: Steve Simon

    > do you have pointers to any documentation on the rand/MIT network API?

There was no 'MIT' network API. He was talking about the CHAOSNet API. The
TCP/IP done in the CSR group at MIT used a totally different API.

The various Unix systems at MIT were pretty well out of touch with each other,
and did not exchange code. The only exceptions were the DSSR (later RTS) and
CSR groups in Tech Sq, who used pretty much the same system.

	Noel


             reply	other threads:[~2017-05-23  1:14 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-23  1:14 Noel Chiappa [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
2017-05-23 13:43 Noel Chiappa
2017-05-23 11:35 Paul Ruizendaal
2017-05-23  1:33 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
     [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
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=20170523011452.99DD518C095@mercury.lcs.mit.edu \
    --to=jnc@mercury.lcs.mit.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).