The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Heinz Lycklama <heinz@osta.com>
To: Paul Ruizendaal <pnr@planet.nl>, TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] non-blocking IO (morphing to "The serial I/O loop")
Date: Tue, 2 Jun 2020 22:41:16 -0700	[thread overview]
Message-ID: <3e482f51-2c2e-19a8-c9fd-f23c67f1df8c@osta.com> (raw)
In-Reply-To: <FE160071-81A7-4FEA-9637-A8DCDF793145@planet.nl>

See comments below.

Heinz

On 6/2/2020 2:34 AM, Paul Ruizendaal wrote:
>> On 5/31/2020 9:46 AM, Warner Losh wrote:
>>> Sorry to top post, but LSX or Miniunix had non blocking I/O as well.
>>> It was in one of the documents that Clem scanned in the last year. It
>>> specifically was an experiment into how to do it.
>>>
>>> Warner
>> I did  add a few new features to LSX to deal with contiguous files
>> and to handle asynchronous read/write's for real time applications.
>> They are described in the LSX paper in the 1978 BSTJ on the
>> UNIX Time-Sharing System.
>>
>> Heinz
> Thanks for highlighting this!
>
> The realm here is async I/O to disk, my original scope was limited to “communication” files (tty’s, pipes, network connections). Still, I find it an interesting topic.
>
> For others, the paper that you refer to can also be found here:
> https://www.tuhs.org/Archive/Documentation/TechReports/Heinz_Tech_Memos/UNIX_on_a_Microprocessor_19780322.pdf
> If I read correctly, the async functionality was available only in the stand alone program version of LSX. Is that correct? In any case, the source code appears lost.
Any source code for LSX would be archived somewhere within
Nokia Bell Labs?
>  From another paper in that set, I get the impression that the async functionality for LSX builds on earlier work for a very early version of Unix:
> https://www.tuhs.org/Archive/Documentation/TechReports/Heinz_Tech_Memos/TM-74-1352-1_Implementation_of_Large_Contiguous_Files_and_Asynchronous_IO_in_UNIX_19740104.pdf
Yes, as this memo describes, I implemented a very simple version
of large contiguous files and asynchronous file I/O for a special
application. The MERT system developed a little later on, had a
completely integrated of implementation of contiguous files
and asynchronous file I/O.
> - - -
>
> When reading through the papers in that TUHS directory, something else caught my attention: early networking at the labs. For a while I have been puzzled by the “serial I/O loop” in use at the labs in the early seventies. Last Fall I found some 1970/1971 BSTJ papers about it, but there it stopped.
Jon Steinhart would have more information about the serial I/O loo.
> I see in the memo on Glance (https://www.tuhs.org/Archive/Documentation/TechReports/Heinz_Tech_Memos/TM-75-1352-3_GLANCE_Terminals_on_UNIX_Time-Sharing_19750303.pdf) that D.R. Weller continued to work on it up to 1973 at least and that it was integrated with Unix in some way. Is that correct? Did the two memo’s referred to (MM 70-1384-1 and TM 73-1356-8) survive?
I do not believe that the software for the Glance terminals was ever
integrated into the standard UNIX software distribution
> Then the memo on satellite processors is very interesting (https://www.tuhs.org/Archive/Documentation/TechReports/Heinz_Tech_Memos/TM-78-3114-2_A_Minicomputer_Satellite_Processor_System_19780322.pdf). This appears to show the serial I/O loop in use as late as 1978, with a very intriguing use case involving system call forwarding over the network.
Carl Christensen and I developed this software to handle small
computer systems with disk storage, as described in the memo,
and in the BSTJ article. The satellite diskless computers could be attached
to a powerful central computer by means the serial I/O loop or
various standard DEC controllers. Each of the satellite computers
could run different tailored applications
> Can you tell me more about the serial I/O loop and its use cases?
I think Jon Steinhart has described this elsewhere?
>
>
>
>


      reply	other threads:[~2020-06-03  5:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02  9:34 Paul Ruizendaal
2020-06-03  5:41 ` Heinz Lycklama [this message]

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=3e482f51-2c2e-19a8-c9fd-f23c67f1df8c@osta.com \
    --to=heinz@osta.com \
    --cc=pnr@planet.nl \
    --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).