From: hooanon05@yahoo.co.jp Subject: Re: [RFC] Union Mount: Readdir approaches Date: Mon, 10 Sep 2007 11:16:43 +0900 Message-ID: References: <20070907054618.GD1692@in.ibm.com> <20070907075855.GG1692@in.ibm.com> <20070907173941.GB20360@filer.fsl.cs.sunysb.edu> Cc: Bharata B Rao , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, hch@infradead.org, Jan Blunck To: "Josef 'Jeff' Sipek" Return-path: Received: from vsmtp01.dti.ne.jp ([202.216.231.136]:47508 "EHLO vsmtp01.dti.ne.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753794AbXIJCRu (ORCPT ); Sun, 9 Sep 2007 22:17:50 -0400 In-Reply-To: <20070907173941.GB20360@filer.fsl.cs.sunysb.edu> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hello Jeff, "Josef 'Jeff' Sipek": > Unless I missunderstood something, Unionfs uses the same approach. Even > Unionfs's ODF branch does the same thing. The major difference is that we > keep the cache in a file on a disk. The approach unionfs-2.1.2 took differs from mine. Major difference is, - in this approach, the cache in struct file is the completed virtual disk block for the dir. - readdir doesn't have to call vfs_readdir when the cache exists and is valid. simply calls filldir. - it supports SEEK_END. Junjiro Okajima