Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 27 Feb 2003 17:15:55 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 27 Feb 2003 17:15:55 -0500 Received: from astound-64-85-224-253.ca.astound.net ([64.85.224.253]:43018 "EHLO master.linux-ide.org") by vger.kernel.org with ESMTP id ; Thu, 27 Feb 2003 17:15:53 -0500 Date: Thu, 27 Feb 2003 13:57:47 -0800 (PST) From: Andre Hedrick To: Scott Lee cc: linux-kernel@vger.kernel.org, axboe@suse.de Subject: Re: [PATCH] ide write barriers In-Reply-To: <200302262031.MAA18505@redhot.rose.hp.com> Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 898 Lines: 25 On Wed, 26 Feb 2003, Scott Lee wrote: > > The goal is to make the use of write > > back cache enabled ide drives safe with journalled file systems. > > Does this mean that having write caching enabled is not safe if you are > using ext3 on an IDE drive? Should "hdparm -W 0 /dev/hda" be used for > example. (I see a 50% performance hit using "-W 0" when my box is under > load.) If this is the case, what is the root cause? Do IDE drives > reorder writes when they are cached? All drives reorder unless instructed not to do so. ATA drives are just now getting FUA hooks. So flush cache often. Cheers, Andre Hedrick LAD Storage Consulting Group - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/