From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bombadil.infradead.org ([65.50.211.133]:41019 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750746AbdFNGqV (ORCPT ); Wed, 14 Jun 2017 02:46:21 -0400 Date: Tue, 13 Jun 2017 23:46:19 -0700 From: Christoph Hellwig Subject: Re: XFS journal write ordering constraints? Message-ID: <20170614064619.GA3598@infradead.org> References: <20170609234408.GE17542@dastard> <20170612235002.GF17542@dastard> <20170613221647.GG17542@dastard> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170613221647.GG17542@dastard> Sender: linux-xfs-owner@vger.kernel.org List-ID: List-Id: xfs To: Dave Chinner Cc: Sweet Tea Dorminy , linux-xfs@vger.kernel.org On Wed, Jun 14, 2017 at 08:16:47AM +1000, Dave Chinner wrote: > Yes, that's my understanding, too, but I also thought that multiple > outstanding flushes are ordered by the block layer. i.e. flushes can > be reordered against other operations, but not other flushes. There is no such guarantee. For request based drivers some ordering happens in practice, but that's an implementation artifact and not a gurantee, and for bio based drivers all bets are off.