Xref: utzoo comp.protocols.nfs:1905 comp.arch:21321
Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!ukma!usenet.ins.cwru.edu!agate!ucbvax!dog.ee.lbl.gov!elf.ee.lbl.gov!torek
From: torek@elf.ee.lbl.gov (Chris Torek)
Newsgroups: comp.protocols.nfs,comp.arch
Subject: Re: Incremental sync()s and using disk idle time
Message-ID: <10773@dog.ee.lbl.gov>
Date: 9 Mar 91 00:26:10 GMT
References: <28975@cs.yale.edu> <PCG.91Feb28195347@odin.cs.aber.ac.uk> <PCG.91Mar4210505@aberdb.cs.aber.ac.uk> <1991Mar5.223443.21187@ns.uoregon.edu> <1991Mar6.003008.9131@bellcore.bellcore.com> <1991Mar7.115154.4820@hq.demos.su> <1991Mar8.142031.9098@bellcore.bellcore.com>
Reply-To: torek@elf.ee.lbl.gov (Chris Torek)
Organization: Lawrence Berkeley Laboratory, Berkeley
Lines: 13
X-Local-Date: Fri, 8 Mar 91 16:26:10 PST

In article <1991Mar8.142031.9098@bellcore.bellcore.com>
mo@messy.bellcore.com (Michael O'Dell) writes:
>[much about disk queue sorting]

Of course, certain disk controllers (whose names I shall not name)
have a tendency to swallow up a whole bunch of I/O requests and do
them in its own order, rather than listen to / allow you to adjust
yours....

Sometimes I think we need a Coalition to Stamp Out `Smart' I/O Devices,
-- 
In-Real-Life: Chris Torek, Lawrence Berkeley Lab EE div (+1 415 486 5427)
Berkeley, CA		Domain:	torek@ee.lbl.gov