Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!uunet!caen!sdd.hp.com!usc!news From: merlin@neuro.usc.edu (merlin) Newsgroups: comp.unix.bsd Subject: Re: Take out fs cache! Date: 13 Jul 1992 15:29:50 -0700 Organization: University of Southern California, Los Angeles, CA Lines: 20 Sender: merlin@neuro.usc.edu (merlin) Message-ID: <l640uuINN4cj@neuro.usc.edu> References: <1992Jul9.141010.2324@ntuix.ntu.ac.sg> <wutcd.710795614@hrz.tu-chemnitz.de> NNTP-Posting-Host: neuro.usc.edu How about implementing an optional configurable file system cache? In some environments (e.g. end user systems target to support more or less one user running a dedicated application which requires a unix environment [unix utilities, unix system calls, gcc, TCP/IP, RPC, NFS, X11R4/R5]) it might make sense to completely disable the buffer cache so power failures don't generate extensive filesystem cleaning problems. In other environments a static cache would be appropriate. In yet other environments perhaps a dynamic cache. Would eliminating the file system cache in the presence of a smart disk controller (Adaptec 1542b SCSI) create horrendous performance problems in the single user, foreground/background multiapplication environment? Or would it achieve the desirable end of not messing up the filesystem (which consequently requires cleaning) when power is either accidentally or intentionally removed before more formal shutdown processes are executed? Thanks, AJ