Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!security!genrad!decvax!harpo!seismo!hao!hplabs!sri-unix!LEVITT%MIT-OZ@MIT-MC.ARPA
From: LEVITT%MIT-OZ@MIT-MC.ARPA
Newsgroups: net.works
Subject: more on memory architecture
Message-ID: <14640@sri-arpa.UUCP>
Date: Thu, 22-Dec-83 00:48:00 EST
Article-I.D.: sri-arpa.14640
Posted: Thu Dec 22 00:48:00 1983
Date-Received: Tue, 20-Dec-83 01:18:23 EST
Lines: 15

emory still isn't free.  On the other hand, I've seen a PDP-11 do
real-time music IO, graphics, print files, etc. simultaneously, all
with less memory than the Lisa.  They keys are interrupts, a small
and/or segmented kernel, and careful memory organization in general.

I was serious when I asked about software development systems that
support assisted or automatic segment management, and I hope someone
responds.  I'm amazed at the number of people who assume demand paging
is cost-effective and necessary.

I'd like to know what other designers think.  Is there an inherently
large, unsegmentable kernel in any system you can imagine finding
satisfactory?  Is it too much trouble to think about and implement
more structured ways of organizing the system - so it will only become
cost effective when someone else builds a good tool?