From mboxrd@z Thu Jan 1 00:00:00 1970 From: jim owens Subject: Re: [PATCH 0/4] Fiemap, an extent mapping ioctl - round 2 Date: Tue, 08 Jul 2008 10:39:56 -0400 Message-ID: <48737C3C.9020605@hp.com> References: <20080625221835.GQ28100@wotan.suse.de> <1214489061.6237.16.camel@norville.austin.ibm.com> <4863A483.5060303@redhat.com> <1214490465.6237.24.camel@norville.austin.ibm.com> <486C13B7.4030402@hp.com> <20080703111726.GZ29319@disturbed> <486CC446.1050602@hp.com> <0371AF9C-A83A-4584-83D2-6EE9DCEACD77@cam.ac.uk> <4872A044.7070001@hp.com> <20080708015153.GM11558@disturbed> <4873657C.3020601@hp.com> <487373AF.1030309@hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org To: Dave Chinner Return-path: Received: from g4t0014.houston.hp.com ([15.201.24.17]:25979 "EHLO g4t0014.houston.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753327AbYGHOkB (ORCPT ); Tue, 8 Jul 2008 10:40:01 -0400 In-Reply-To: <487373AF.1030309@hp.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: Assuming I am correct in at least part of my understanding on why there is > * FIEMAP_FLAG_SYNC > If this flag is set, the kernel will sync the file before mapping extents. I propose we replace it with the following flag that should provide everything XFS needs: * FIEMAP_FLAG_ANY * Advisory only - If this flag is set, the filesystem can * ignore normal consistency checks when returning data. Then with the flag==0, XFS does the locked-atomic-sync and with the flag==1, XFS works like other filesystems that don't do the atomic stuff. jim