From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Howells Subject: Re: [PATCH 1/4] CacheFiles: Use the ->write() file op rather than a special kernel aop Date: Fri, 03 Apr 2009 10:51:56 +0100 Message-ID: <9759.1238752316@redhat.com> References: <20090403094138.9510.80681.stgit@warthog.procyon.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: dhowells@redhat.com, linux-fsdevel@vger.kernel.org, nfsv4@linux-nfs.org, linux-kernel@vger.kernel.org To: nickpiggin@yahoo.com.au, hch@infradead.org Return-path: In-Reply-To: <20090403094138.9510.80681.stgit@warthog.procyon.org.uk> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: nfsv4-bounces@linux-nfs.org Errors-To: nfsv4-bounces@linux-nfs.org List-Id: linux-fsdevel.vger.kernel.org David Howells wrote: > This reverts the patch: > > CacheFiles: Add a hook to write a single page of data to an inode > > Add an address space operation to write one single page of data to an > inode at a page-aligned location (thus permitting the implementation to > be highly optimised). The data source is a single page. > > This is used by CacheFiles to store the contents of netfs pages into > their backing file pages. > > Supply a generic implementation for this that uses the write_begin() > and write_end() address_space operations to bind a copy directly into > the page cache. > > Hook the Ext2 and Ext3 operations to the generic implementation. Actually, it doesn't. I split that out into the next patch, but I forgot to edit the patch description. David