From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262582AbTJNPdF (ORCPT ); Tue, 14 Oct 2003 11:33:05 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262587AbTJNPdF (ORCPT ); Tue, 14 Oct 2003 11:33:05 -0400 Received: from ns.virtualhost.dk ([195.184.98.160]:14279 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id S262582AbTJNPdD (ORCPT ); Tue, 14 Oct 2003 11:33:03 -0400 Date: Tue, 14 Oct 2003 17:31:56 +0200 From: Jens Axboe To: Andi Kleen Cc: Andi Kleen , linux-kernel@vger.kernel.org Subject: Re: [PATCH] ide barrier support, #2 Message-ID: <20031014153156.GU1107@suse.de> References: <20031014125723.GR1107@suse.de> <20031014150807.GA99122@colin2.muc.de> <20031014151230.GS1107@suse.de> <20031014152826.GA9391@colin2.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20031014152826.GA9391@colin2.muc.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 14 2003, Andi Kleen wrote: > > See the patch, WRITESYNC is used solely internally in raid1. > > WRITEBARRIER is a bitmask of BIO_RW and BIO_RW_BARRIER and that is what > > you want. I'll make that more clear. Writes will not be reordered around > > the barrier either, btw. > > It would be still misnamed. I want a flush and not a barrier. Don't you still require previously submitted writes to have hit platter before your flush goes down? > Anyways, when you apply the patch just change the cmd that what > you think is right. I did :) -- Jens Axboe