From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from verein.lst.de ([213.95.11.211]:35272 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750915AbcGAFE6 (ORCPT ); Fri, 1 Jul 2016 01:04:58 -0400 Date: Fri, 1 Jul 2016 07:04:55 +0200 From: Christoph Hellwig To: Damien Le Moal Cc: Christoph Hellwig , Amir Goldstein , Ming Lei , linux-fsdevel , linux-block , Jens Axboe Subject: Re: Question about loop device DIO/AIO and FLUSH Message-ID: <20160701050455.GA828@lst.de> References: <20160701042510.GA381@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Jul 01, 2016 at 05:00:18AM +0000, Damien Le Moal wrote: > Did you mean "...I/O requests that have already been fully submitted" ? No. > Flushing I/Os that have already completed does not seem > to make much sense. Or I am also missing something... With a volatile write cache this makes a lot of sense. And fsync flushes the volatile fs metadata to disk, while flush flushes the volatile disk write cache.