Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site utcsrgv.UUCP
Path: utzoo!utcsrgv!mason
From: mason@utcsrgv.UUCP (Dave Mason)
Newsgroups: net.unix-wizards
Subject: Interprocess Communication: Messages & Monitors
Message-ID: <2307@utcsrgv.UUCP>
Date: Wed, 21-Sep-83 19:59:28 EDT
Article-I.D.: utcsrgv.2307
Posted: Wed Sep 21 19:59:28 1983
Date-Received: Wed, 21-Sep-83 20:28:18 EDT
Organization: CSRG, University of Toronto
Lines: 48

I've been reading all these wise words, but have decided I should add my
two cents worth.  (This is the subject of my M.Sc. thesis, in progress).

First to clear up one misconception: Someone asked why Unix couldn't
ignore uncaught signals rather than abort.  The obvious answer (which is
often the RIGHT answer, tho not always) is that there would then be no
way to stop a runaway (dare I say "rogue") program.

There have been several suggestions that the proper approach is one using
signals or ASTs, or in other words *interrupts*.  Much work has been done
in the recent past to design high-level languages that include the concept
of concurrency primarily in order to be able to write operating systems and
other stand-alone programs in a way that would avoid the concept of asynchronous
interrupts.  Note that this was done so that the "system programmers",
presumably good programmers already familiar with these concepts, could be
enabled to write clearer, more correct, more robust systems.  (For refs:
Lampson & Redell,CACM (23,2); Cheriton et al.,CACM (22,1); Holt: Concurrent
Euclid, Unix & Tunis, Addison-Wesley 1982; Wirth's Lillith stuff (sorry no
refs))  It seems reasonable to assume that many of the people who wish to
do IPC lack much of the feeling for interrupts that has been a mark of the
system programmer.

Once we agree that interrupts aren't the way to go, we are left with 2 choices:
"message based" or "procedure oriented"(monitors etc.)  (See Lauer & Needham,
ACM O/S Review (13,2); or an EXCELLENT paper by Cashin on IPC, Bell Northern
Research #8005014)  Named pipes can give effectively the message based model
(although as was pointed out, byte oriented is a problem).  The 4.2 stuff
appears to give a reasonable implementation (when it works) of message
based concurrency (although some of it seems a little kludgy (all this from
prelim documentation)).  Pipes are a great idea, but for I/O redirection,
NOT interprocess communication.

At UofToronto we have a procedure oriented concurrency language called
Concurrent Euclid (CE) which was used to write the Unix work-alike Tunis.
(See Holt82; Cordy & Holt: Specification of CE, U of Toronto report CSRG-133,
1981)
The major part of my thesis will be to migrate the concepts of monitors into
the operating system so that one can write CE programs that can take full
advantage of the concurrency available to the operating system (multi-
processors etc.) (at least that is the plan.  My supervisor and I have
to decide on implementation in the next couple of weeks.  Note that the
opinions expressed here are mine and doot neccessarily reflect those of
my supervisor or anyone else.)
I could say more, but this is already longer than most news articles I'll
read.  I'm open to comments, questions, and (shudder) flames.
 --   Dave Mason, U. Toronto CSRG,
        {cornell,watmath,ihnp4,floyd,allegra,utzoo,uw-beaver}!utcsrgv!mason
     or {decvax,linus,research}!utzoo!utcsrgv!mason   (UUCP)