Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ptsfa!ihnp4!ihopa!jdu
From: jdu@ihopa.ATT.COM (John Unruh)
Newsgroups: comp.arch,comp.os.misc
Subject: Re: OS co-processor ??
Message-ID: <584@ihopa.ATT.COM>
Date: Thu, 8-Oct-87 08:59:14 EDT
Article-I.D.: ihopa.584
Posted: Thu Oct  8 08:59:14 1987
Date-Received: Sun, 11-Oct-87 09:58:05 EDT
References: <2272@umn-cs.UUCP>
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 14
Summary: CDC Operating Systems
Xref: mnetor comp.arch:2563 comp.os.misc:278

In article <2272@umn-cs.UUCP>, amit@umn-cs.UUCP (Neta Amit) writes:
> We're are looking into a co-processor that takes over certain OS tasks.
> Specifically, we're thinking about scheduling, interrupts and swaps.
> Possibly deadlock resolution.
> 
> Any thoughts? References to the literature?

If I remember correctly, many (if not all) of the CDC 6000 series computers
used operating systems that ran mostly in the peripheral processors.  This
freed the CPU to crunch numbers.  Some of these operating systems were 
fairly efficeint, but I never used one that was "nice" for an interactive
user.  They seemed to be very good at batch throughput.
                                  John Unruh
                                  ihnp4!ihlpk!jdu