Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!rpi!batcomputer!cornell!rochester!rit!tropix!moscom!ur-valhalla!uhura.cc.rochester.edu!sunybcs!rutgers!tut.cis.ohio-state.edu!ucbvax!hplabs!hp-sdd!ncr-sd!serene!rfarris
From: rfarris@serene.UUCP (Rick Farris)
Newsgroups: comp.unix.xenix
Subject: Re: Caching disk controllers and 386 multiprocessor
Keywords: multiprocessing, disk controller
Message-ID: <725@serene.UUCP>
Date: 22 Jul 89 03:08:21 GMT
References: <1013@aber-cs.UUCP> <10870@nuchat.UUCP>
Reply-To: rfarris@serene.UU.NET (Rick Farris)
Organization: Serenity BBS, Del Mar, California
Lines: 14

In article <10870@nuchat.UUCP> steve@nuchat.UUCP (Steve Nuchia) writes:
> There are exceptions to the general rule that more main memory for
> the unix block cache beats caching controllers and ram disks.

I've been watching this discussion for several days now, and I've
noticed that no-one has mentioned the biggest advantage of the DPT
controller:  It has an on-board computer!  We're talking
multi-processing, folks.  The main cpu can write to the controllers
cache, and then the cpu on the controller can do the elevator writes,
etc, *at the same time the main cpu is doing other things.*


Rick Farris   RF Engineering  POB M  Del Mar, CA  92014   voice (619) 259-6793
rfarris@serene.uu.net      ...!uunet!serene!rfarris       serene.UUCP 259-7757