From mboxrd@z Thu Jan 1 00:00:00 1970 From: Werner Almesberger Subject: Re: barriers vs. reads Date: Tue, 22 Jun 2004 15:45:32 -0300 Sender: linux-fsdevel-owner@vger.kernel.org Message-ID: <20040622154532.F1325@almesberger.net> References: <20040622005302.A1325@almesberger.net> <20040622073919.GV12881@suse.de> <20040622045004.C1325@almesberger.net> <20040622075531.GX12881@suse.de> <20040622112802.GA21456@mail.shareable.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Jens Axboe , linux-fsdevel@vger.kernel.org Return-path: Received: from almesberger.net ([63.105.73.238]:32524 "EHLO host.almesberger.net") by vger.kernel.org with ESMTP id S265368AbUFVSps (ORCPT ); Tue, 22 Jun 2004 14:45:48 -0400 To: Jamie Lokier Content-Disposition: inline In-Reply-To: <20040622112802.GA21456@mail.shareable.org>; from jamie@shareable.org on Tue, Jun 22, 2004 at 12:28:02PM +0100 List-Id: linux-fsdevel.vger.kernel.org Jamie Lokier wrote: > 1. A read _which doesn't overlap writes before the barrier_ > should be ok before the barrier with no visible change. Ah, that's an excellent point. Thanks ! - Werner -- _________________________________________________________________________ / Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net / /_http://www.almesberger.net/____________________________________________/