From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [RFC][PATCH 0/5] Fiemap, an extent mapping ioctl Date: Thu, 29 May 2008 09:02:54 -0400 Message-ID: <20080529130254.GB21299@infradead.org> References: <20080525000148.GJ8325@wotan.suse.de> <20080525194203.GB24328@infradead.org> <20080527185622.GR8325@wotan.suse.de> <20080527203124.GC27827@mail.oracle.com> <20080528160201.GA7263@webber.adilger.int> <20080528170419.GA6031@mail.oracle.com> <20080529005134.GB12405@disturbed> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: Joel Becker , Andreas Dilger , Mark Fasheh , Christoph Hellwig , linux-fsdevel@vger.kernel.org, Andreas Return-path: Received: from bombadil.infradead.org ([18.85.46.34]:57294 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755136AbYE2NC4 (ORCPT ); Thu, 29 May 2008 09:02:56 -0400 Content-Disposition: inline In-Reply-To: <20080529005134.GB12405@disturbed> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, May 29, 2008 at 10:51:34AM +1000, Dave Chinner wrote: > XFS has XFS_IOC_FSGETXATTR which can return the number of extents > on an inode. It's a total count, not a range count, so it's a bit > different to FIECOUNT and as such does not require walking the > extent list to retrieve (extent count is in the inode itself). What use is there geeting the extent count for a range? I'd rather do it only per-file like the xfs ioctl. > It's still not that straight forward as you have to encode count, > offset and length into a structure to pass into the ioctl. i.e. > is it really that much simpler and cleaner than just adding a > extra flag to FIEMAP? Yes :)