Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!uwvax!dan
From: dan@rsch.wisc.edu (Daniel M. Frank)
Newsgroups: net.unix-wizards
Subject: Re: RAM disk vs paging + buffer cache
Message-ID: <2603@rsch.wisc.edu>
Date: Thu, 14-Aug-86 01:35:43 EDT
Article-I.D.: rsch.2603
Posted: Thu Aug 14 01:35:43 1986
Date-Received: Thu, 14-Aug-86 08:29:17 EDT
References: <514@opus.nbires.UUCP> <381@nitrex.UUCP>
Sender: news@rsch.wisc.edu
Reply-To: dan@rsch.wisc.edu (Daniel M. Frank)
Organization: /usr/lib/news/organization
Lines: 19

In article <381@nitrex.UUCP> rbl@nitrex.UUCP ( Dr. Robin Lake ) writes:
>
>Note:  if a device driver is required, much of the inherent speed advantage
>is lost.  Drivers consume milliseconds per access, not very noticible when
>disk latency is tens to hundreds of milliseconds.  When RAM is accessed,
>rotational and seek latency go away and the driver delays are very noticable.

   Ok, I give up.  Did you hack the file system or buffer cache code to
access the RAM directly?  If not, how did you avoid using device drivers?


------

      Dan Frank

	  Q: What's the difference between an Apple MacIntosh
	     and an Etch-A-Sketch?

	  A: You don't have to shake the Mac to clear the screen.