Message-ID: <4069F6F0.305@pobox.com>
Date: Tue, 30 Mar 2004 17:38:40 -0500
From: Jeff Garzik <jgarzik@pobox.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030703
MIME-Version: 1.0
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
CC: "Stephen C. Tweedie" <sct@redhat.com>, Chris Mason <mason@suse.com>,
       Jens Axboe <axboe@suse.de>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] barrier patch set
References: <20040319153554.GC2933@suse.de> <1080683417.1978.53.camel@sisko.scot.redhat.com> <4069F2FC.90003@pobox.com> <200403310040.43034.bzolnier@elka.pw.edu.pl>
In-Reply-To: <200403310040.43034.bzolnier@elka.pw.edu.pl>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 977
Lines: 30

Bartlomiej Zolnierkiewicz wrote:
> On Wednesday 31 of March 2004 00:21, Jeff Garzik wrote:
> 
>>Stephen C. Tweedie wrote:
>>
>>>Yep.  It scares me to think what performance characteristics we'll start
>>>seeing once that gets used everywhere it's needed, though.  If every raw
>>>or O_DIRECT write needs a flush after it, databases are going to become
>>>very sensitive to flush performance.  I guess disabling the flushing and
>>>using disks which tell the truth about data hitting the platter is the
>>>sane answer there.
>>
>>For IDE, O_DIRECT and O_SYNC can use special "FUA" commands, which don't
>>return until the data is on the platter.
> 
> 
> Do you know of any drive supporting it?  I don't.


Newer SATAs do...

	Jeff


-
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/