From owner-freebsd-fs Thu Sep 21 14:20:37 2000 Delivered-To: freebsd-fs@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 7AADE37B42C; Thu, 21 Sep 2000 14:20:34 -0700 (PDT) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id OAA07354; Thu, 21 Sep 2000 14:18:06 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp04.primenet.com, id smtpdAAA_qai7n; Thu Sep 21 14:17:46 2000 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id OAA17349; Thu, 21 Sep 2000 14:20:00 -0700 (MST) From: Terry Lambert Message-Id: <200009212120.OAA17349@usr08.primenet.com> Subject: Re: disable write caching with softupdates? To: archie@whistle.com (Archie Cobbs) Date: Thu, 21 Sep 2000 21:20:00 +0000 (GMT) Cc: mbendiks@eunet.no (Marius Bendiksen), sos@freebsd.org, fs@freebsd.org, terry@lambert.org In-Reply-To: <200009211702.KAA13662@bubba.whistle.com> from "Archie Cobbs" at Sep 21, 2000 10:02:16 AM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Please make this conditional, as people with non-crippled hardware might > > want to employ the write cache. A sysctl or build option would be best. > > Yep, that was what I was originally suggesting. > > Soren do you want me to try to come up with a patch? > I don't claim to understand IDE technology.. can you > just send the disable command at any time or is it > more complicated than that? I would also send a flush command. I would be skeptical of an IDE drive perhaps disabling the cache, and leaving the thing dirty. Not knowing the exact details of when the cache control may be changed, I can't say for sure (it may have to be done by the BIOS at boot time, for all I know. If you go over to my cube, there is a full technical specification of the ATA stuff for the Quantum drives we used to use in the InterJet II, prior to the IBM acquisition, and it has this information in it, in detail. Yung gave me the documentation when Julian and I were trying to figure out how much DC holdup was required after an AC failure for us to be able to ensure that thee was no sector corruptions, and that the outstanding operations on the drive were committed, after throwing a pin into the soft updates clock to ensure that no more writes were scheduled. FWIW... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message