From: Josef Sipek Subject: Re: Wrapper fs Code (wrapfs) Date: Tue, 8 Aug 2006 11:41:55 -0400 Message-ID: <20060808154155.GA1654@filer.fsl.cs.sunysb.edu> References: <20060807065904.GA18638@filer.fsl.cs.sunysb.edu> <20060808075729.58361.qmail@web37504.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from filer.fsl.cs.sunysb.edu ([130.245.126.2]:23765 "EHLO filer.fsl.cs.sunysb.edu") by vger.kernel.org with ESMTP id S964960AbWHHPmJ (ORCPT ); Tue, 8 Aug 2006 11:42:09 -0400 To: UZAIR LAKHANI Content-Disposition: inline In-Reply-To: <20060808075729.58361.qmail@web37504.mail.mud.yahoo.com> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Tue, Aug 08, 2006 at 12:57:29AM -0700, UZAIR LAKHANI wrote: > --- Josef Sipek wrote: > > The data is cached in the page cache. > > Can we not by some way invalidate the old page and > force the kernel to read the actual page i.e. can we > not by any way by-pass the page cache for wrapfs read. Currently, no. We (the stackable fs) would need to invalidate the page associated with ext3. ext3 won't invalidate our pages, so we would have to do it ourselves. To do that, we'd need some kind of callback so that when an ext3 page changes, we can propagate the change. > How ext3 e.g. always get the updated data on read. I am not sure what you mean. Josef "Jeff" Sipek. -- The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. - George Bernard Shaw