Path: utzoo!attcan!uunet!lll-winken!sun-barr!ccut!titcca!cc.titech.ac.jp!necom830!mohta
From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
Newsgroups: comp.arch
Subject: Fast /tmp (was Re: Mixing paging and IO is inefficient)
Message-ID: <5784@titcce.cc.titech.ac.jp>
Date: 5 Jul 90 11:41:31 GMT
References: <499@garth.UUCP> <5660@titcce.cc.titech.ac.jp> <137770@sun.Eng.Sun.COM> <103@array.UUCP>
Sender: news@cc.titech.ac.jp
Organization: Tokyo Institute of Technology
Lines: 17

In article <103@array.UUCP> colin@array.UUCP (Colin Plumb) writes:

>>Trying to solve this problem in the manner described in Ohta's Usenix paper 
>>is a mistake.  It's an inapproriate solution to the problem.

>I think it's a wierd hybrid of a ramdisk and stable storage, and I
>think it's ugly, but I can't say it's *wrong*.

It is an interesting point of view to see UNIX buffer cache mechanism
a wierd bybrid of a ramdisk and stable storage.

As I added almost nothing and just used an existing mechanism, you
are offending UNIX buffer chache mechanism itself.

You may think buffer cache is ugly, but to me, it is just fine.

					Masataka Ohta