From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.suse.de (mx2.suse.de [195.135.220.15]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id CC0272095B9C6 for ; Thu, 24 Aug 2017 05:32:18 -0700 (PDT) Date: Thu, 24 Aug 2017 14:34:51 +0200 From: Jan Kara Subject: Re: [PATCH 11/13] dax, iomap: Add support for synchronous faults Message-ID: <20170824123451.GA6187@quack2.suse.cz> References: <20170817160815.30466-1-jack@suse.cz> <20170817160815.30466-12-jack@suse.cz> <20170824122720.GA9961@infradead.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20170824122720.GA9961@infradead.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: linux-nvdimm-bounces@lists.01.org Sender: "Linux-nvdimm" To: Christoph Hellwig Cc: Boaz Harrosh , Jan Kara , linux-nvdimm@lists.01.org, linux-xfs@vger.kernel.org, Andy Lutomirski , linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org List-ID: On Thu 24-08-17 05:27:20, Christoph Hellwig wrote: > Just curious: how does IOMAP_F_NEEDDSYNC practically differ > from IOMAP_F_NEW? In a subtle but important way ;). The main difference is that if the extent has been already allocated by previous write, but the changing transaction is not yet committed, we will return IOMAP_F_NEEDDSYNC but not IOMAP_F_NEW. Honza -- Jan Kara SUSE Labs, CR _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm