From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: NFSv4/pNFS possible POSIX I/O API standards Date: Thu, 30 Nov 2006 09:25:48 +0000 Message-ID: <20061130092548.GA1534@infradead.org> References: <6.2.3.4.2.20061127213243.04f786c0@cic-mail.lanl.gov> <20061128055428.GA29891@infradead.org> <20061129090450.GA16296@infradead.org> <20061129094815.GE6429@schatzie.adilger.int> <1164795522.7557.45.camel@imp.csi.cam.ac.uk> <20061129082622.GA20285@cynthia.pants.nu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Anton Altaparmakov , Andreas Dilger , Christoph Hellwig , Gary Grider , linux-fsdevel@vger.kernel.org Return-path: Received: from pentafluge.infradead.org ([213.146.154.40]:28103 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S1759218AbWK3JZ4 (ORCPT ); Thu, 30 Nov 2006 04:25:56 -0500 To: Brad Boyer Content-Disposition: inline In-Reply-To: <20061129082622.GA20285@cynthia.pants.nu> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, Nov 29, 2006 at 12:26:22AM -0800, Brad Boyer wrote: > For a more extreme case, hfs and hfsplus don't even have a separation > between directory entries and inode information. The code creates this > separation synthetically to match the expectations of the kernel. During > a readdir(), the full catalog record is loaded from disk, but all that > is used is the information passed back to the filldir callback. The only > thing that would be needed to return extra information would be code to > copy information from the internal structure to whatever the system call > used to return data to the program. In this case you can infact already instanciate inodes froms readdir. Take a look at the NFS code.