Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.bhp.com.au!mel.dit.csiro.au!munnari.OZ.AU!spool.mu.edu!agate!howland.reston.ans.net!vixen.cso.uiuc.edu!uwm.edu!lll-winken.llnl.gov!venus.sun.com!news2me.EBay.Sun.COM!engnews2.Eng.Sun.COM!peyto!thurlow From: thurlow@peyto.eng.sun.com (Robert Thurlow) Newsgroups: comp.unix.bsd.netbsd.misc,comp.unix.bsd.bsdi.misc,comp.unix.solaris,comp.unix.aix Subject: Re: ISP hardware/software choices (performance comparison) Date: 21 Jan 1996 01:02:54 GMT Organization: Sun Microsystems Computer Corporation Lines: 27 Distribution: inet Message-ID: <4ds3bu$55l@engnews2.Eng.Sun.COM> References: <4d9has$qo9@park.uvsc.edu> <4depms$bi5@park.uvsc.edu> <4dm8d8$30r@engnews2.Eng.Sun.COM> <4dp29j$8v8@park.uvsc.edu> NNTP-Posting-Host: peyto.eng.sun.com Cc: Xref: euryale.cc.adfa.oz.au comp.unix.bsd.netbsd.misc:1953 comp.unix.bsd.bsdi.misc:2097 comp.unix.solaris:57217 comp.unix.aix:68696 In article <4dp29j$8v8@park.uvsc.edu>, Terry Lambert <terry@lambert.org> wrote: >] >Client caching prior to NFSv3 violates the protocol specification. >| void >| NFSPROC_WRITECACHE(void) = 7; >| >| To be used in the next protocol revision. > >Ie: not in this one. That operation was envisioned as a precursor to the NFS V3 safe async write, and has nothing whatsoever to do with client caching. Your initial statement is simply not correct, whatever your interpretation of "transparent" is in this context. What makes you think that client caching in NFS V3 is suddenly and miraculously legal according to the spec? Cache consistency has improved, but it isn't made perfect by any particular operation. Rob T -- Rob Thurlow, thurlow@eng.sun.com There was something fishy about the butler. I think he was a Pisces, probably working for scale. -- Nick Danger, Third Eye